anchor.diff:  The interface gives you one method:
   
   ----
  -    /**
  -    * Method executed upon state change of a dependency
  -    *
  -    * @param dependencyName - alias from microservice configuration {@see ZookeeperDependencies}
  -    * @param newState
  -    */
       void stateChanged(String dependencyName, DependencyState newState);
   ----
   
  
positive.code: ----
  
  [[spring-cloud-zookeeper-dependencies]]
  === Using the Zookeeper Dependencies
  Spring Cloud Zookeeper gives you a possibility to provide dependencies of your application as properties. As dependencies you can understand other applications that are registered
  in Zookeeper and which you would like to call via https://github.com/spring-cloud/spring-cloud-netflix/blob/master/docs/src/main/asciidoc/spring-cloud-netflix.adoc#spring-cloud-feign[Feign] (a REST client builder)
  and also https://github.com/spring-cloud/spring-cloud-netflix/blob/master/docs/src/main/asciidoc/spring-cloud-netflix.adoc#spring-cloud-ribbon[Spring `RestTemplate`].
  
negative.code: 
  
  [[spring-cloud-zookeeper-config]]
  
  == Distributed Configuration with Zookeeper
  
  Zookeeper provides a http://zookeeper.apache.org/doc/current/zookeeperOver.html#sc_dataModelNameSpace[hierarchical namespace] that allows clients to store arbitrary data, such as configuration data.  Spring Cloud Zookeeper Config is an alternative to the https://github.com/spring-cloud/spring-cloud-config[Config Server and Client].  Configuration is loaded into the Spring Environment during the special "bootstrap" phase.  Configuration is stored in the `/config` namespace by default.  Multiple `PropertySource` instances are created based on the application's name and the active profiles that mimicks the Spring Cloud Config order of resolving properties.  For example, an application with the name "testApp" and with the "dev" profile will have the following property sources created:
  