anchor.diff:  
   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:
   
   ----
  
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.
  
  === Registering with Eureka
  
  
negative.code: entries from Eureka.  The Spring Cloud Config Server can be accessed directly
  via host lookup or through the Zuul Proxy.  The non-jvm app should implement
  a health check so the Sidecar can report to eureka if the app is up or down.
  
  To include Sidecar in your project use the dependency with group `org.springframework.cloud`
  and artifact id `spring-cloud-netflix-sidecar`.
  
  To enable the Sidecar, create a Spring Boot application with `@EnableSidecar`.
  This annotation includes `@EnableCircuitBreaker`, `@EnableDiscoveryClient`,
  