anchor.diff:  
   This means that a serviceId "myusers-v1" will be mapped to route
   "/v1/myusers/{all}".  Any regular expression is accepted but all named
  -group must be present in both servicePattern and routePattern.  If
  -servicePattern do not match a serviceId, the default behavior is
  -used. In exemple above, a serviceId "myusers" will be mapped to route
  -"/myusers/{all}" (no version detected) These feature is disable by
  -default and is only applied to discovered services.
  +groups must be present in both servicePattern and routePattern.  If
  +servicePattern does not match a serviceId, the default behavior is
  +used. In the example above, a serviceId "myusers" will be mapped to route
  +"/myusers/{all}" (no version detected) This feature is disable by
  +default and only applies to discovered services.
   
   To add a prefix to all mappings, set `zuul.prefix` to a value, such as
   `/api`. The proxy prefix is stripped from the request before the
  
positive.code:       stripPrefix: false
  ----
  
  In this example requests to "/myusers/101" will be forwarded to "/myusers/101" on the "users" service.
  
  The `zuul.routes` entries actually bind to an object of type `ZuulProperties`. If you
  look at the properties of that object you will see that it also has a "retryable" flag.
  
negative.code:       url: http://example.com/users_service
  ----
  
  These simple url-routes don't get executed as a `HystrixCommand` nor can you loadbalance multiple URLs with Ribbon.
  To achieve this, specify a service-route and configure a Ribbon client for the
  serviceId (this currently requires disabling Eureka support in Ribbon:
  see <<spring-cloud-ribbon-without-eureka,above for more information>>), e.g.
  
  