anchor.diff:      $ cf create-user-provided-service mylogger -r https://logger.cf.example.com
       </pre>
   
  -1. Push a sample app like [Spring Music](https://github.com/cloudfoundry-samples/spring-music). By default this will create a route `spring-music.cf.example.com`.
  +1. Push a sample app like [Spring Music](https://github.com/cloudfoundry-samples/spring-music). By default this creates a route `spring-music.cf.example.com`.
   
       <pre class="terminal">
       $ cf push spring-music
  
positive.code: **Disadvantages:**
  
  - Adding route services requires manual infrastructure configuration.
  - Unnecessary network hops for traffic to apps that do not use the route service; requests for all apps hosted by the deployment pass through the route service component.
  
  ### <a id="user-provided"></a>User-Provided Service ###
  
  If a route service is not listed in the CF marketplace by a broker, a developer can still bind it to their app as a User-Provided service. The service can run anywhere, either inside or outside of CF, but it must fulfill the integration requirements described in [Service Instance Responsibilities](#service-instance-responsibilities). The service also needs to be reachable by an outbound connection from the CF router.
  
  ![User-provided](images/route-services-user-provided.png)
  
  This model is identical to the [fully-brokered service](#fully-brokered) model, except without the broker. Developers configure the service manually, outside of Cloud Foundry. They can then create a user-provided service instance and bind it to their application with the following commands, supplying the URL of their route service:
  
  `cf create-user-provided-service SERVICE_INSTANCE -r ROUTE_SERVICE_URL`
  `cf bind-route-service DOMAIN SERVICE_INSTANCE [--hostname HOSTNAME]`
  
  **Advantages:**
  
  - Adding route services requires no manual infrastructure configuration.
  - Traffic to apps that do not use the service makes fewer network hops; requests for those apps do not pass through the route service.
  
  **Disadvantages:**
  
  - Developers must manually provision/configure route services out of the context of Cloud Foundry; no service broker automates these operations.
  - Traffic to apps that use the route service makes additional network hops, as compared to the static model.
  
  ### <a id="architecture-comparison"></a>Architecture Comparison ###
  
  The models above require the [broker](#broker-responsibilities) and [service instance](#service-instance-responsibilities) responsibilities below, as summarized in the following table:
  
  <table id='architecture-comparison' border="1" class="nice" >
    <tr>
  
negative.code:     $ cf logs logger
      </pre>
  
  1. Send a request to the sample app and view in the route service logs that the request is forwarded to it.
  
      <pre class="terminal">
      $ curl spring-music.cf.example.com
  