anchor.diff:  </dependency>
   ----
   
  -=== Alternatives to the native Netflix EurekaClient
  -
  -You don't have to use the raw Netflix `EurekaClient` and usually it
  -is more convenient to use it behind a wrapper of some sort. Spring
  -Cloud has support for <<spring-cloud-feign, Feign>> (a REST client
  -builder) and also <<spring-cloud-ribbon, Spring `RestTemplate`>> using
  -the logical Eureka service identifiers (VIPs) instead of physical
  -URLs. To configure Ribbon with a fixed list of physical servers you
  -can simply set `<client>.ribbon.listOfServers` to a comma-separated
  -list of physical addresses (or hostnames), where `<client>` is the ID
  -of the client.
  -
  -You can also use the `org.springframework.cloud.client.discovery.DiscoveryClient`
  -which provides a simple API for discovery clients that is not specific
  -to Netflix, e.g.
  +=== Alternatives to the Native Netflix EurekaClient
  +
  +You need not use the raw Netflix `EurekaClient`.
  +Also, it is usually more convenient to use it behind a wrapper of some sort.
  +Spring Cloud has support for <<spring-cloud-feign, Feign>> (a REST client builder) and <<spring-cloud-ribbon, Spring `RestTemplate`>> through the logical Eureka service identifiers (VIPs) instead of physical URLs.
  +To configure Ribbon with a fixed list of physical servers, you can set `<client>.ribbon.listOfServers` to a comma-separated list of physical addresses (or hostnames), where `<client>` is the ID of the client.
  +
  +You can also use the `org.springframework.cloud.client.discovery.DiscoveryClient`, which provides a simple API (not specific to Netflix) for discovery clients, as shown in the following example:
   
   ----
   @Autowired
  
positive.code: 
  == Service Discovery: Eureka Clients
  
  Service Discovery is one of the key tenets of a microservice based architecture. Trying to hand configure each client or some form of convention can be very difficult to do and can be very brittle.  Eureka is the Netflix Service Discovery Server and Client.  The server can be configured and deployed to be highly available, with each server replicating state about the registered services to the others.
  
  [[netflix-eureka-client-starter]]
  === How to Include Eureka Client
  
  To include Eureka Client in your project use the starter with group `org.springframework.cloud`
  and artifact id `spring-cloud-starter-netflix-eureka-client`. See the http://projects.spring.io/spring-cloud/[Spring Cloud Project page]
  for details on setting up your build system with the current Spring Cloud Release Train.
  
  === Registering with Eureka
  
  When a client registers with Eureka, it provides meta-data about itself
  such as host and port, health indicator URL, home page etc.  Eureka
  receives heartbeat messages from each instance belonging to a service.
  If the heartbeat fails over a configurable timetable, the instance is
  normally removed from the registry.
  
  Example eureka client:
  
  [source,java,indent=0]
  ----
  
negative.code: 	public Object run() {
  		RequestContext context = RequestContext.getCurrentContext();
      	HttpServletResponse servletResponse = context.getResponse();
  		servletResponse.addHeader("X-Sample", UUID.randomUUID().toString());
  		return null;
  	}
  }
  ----
  
  NOTE: Other manipulations, such as transforming the response body, are much more complex and computationally intensive.
  
  ==== How Zuul Errors Work
  
  If an exception is thrown during any portion of the Zuul filter lifecycle, the error filters are executed.
  The `SendErrorFilter` is only run if `RequestContext.getThrowable()` is not `null`.
  It then sets specific `javax.servlet.error.*` attributes in the request and forwards the request to the Spring Boot error page.
  
  ==== Zuul Eager Application Context Loading
  
  Zuul internally uses Ribbon for calling the remote URLs.
  By default, Ribbon clients are lazily loaded by Spring Cloud on first call.
  This behavior can be changed for Zuul by using the following configuration, which results eager loading of the child Ribbon related Application contexts at application startup time.
  The following example shows how to enable eager loading:
  
  .application.yml
  ----
  