anchor.diff:  == 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-eureka`. 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
   
  
positive.code: [[spring-cloud-eureka-server]]
  == Service Discovery: Eureka Server
  
  Example eureka server (e.g. using spring-cloud-starter-eureka-server to set up the classpath):
  
  [source,java,indent=0]
  ----
  
negative.code: 
  Having an open circuit stops cascading failures and allows overwhelmed or failing services time to heal.  The fallback can be another Hystrix protected call, static data or a sane empty value.  Fallbacks may be chained so the first fallback makes some other business call which in turn falls back to static data.
  
  
  [[netflix-hystrix-starter]]
  === How to Include Hystrix
  
  To include Hystrix in your project use the starter with group `org.springframework.cloud`
  and artifact id `spring-cloud-starter-hystrix`. 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.
  
  Example boot app:
  
  ----
  