Open subes opened 4 years ago
Though making the current service registry fault-tolerant (instead of being a single point of failure) might be the actual goal. If that is done by a custom simple implementation or by using another service registry implementation does not matter much.
Though in the past using JUDDI was too slow/cumbersome. That is why the custom developed minimal solution was implemented. Zookeeper seemed to be too resource intensive and too complex for our simple needs.
https://spring.io/blog/2015/01/20/microservice-registration-and-discovery-with-spring-cloud-and-netflix-s-eureka
Maybe use the newly created spring-cloud abstractions for the service registry client to make the backend switchable. https://github.com/spring-cloud/spring-cloud-commons/blob/master/spring-cloud-commons/src/main/java/org/springframework/cloud/client/discovery/DiscoveryClient.java
Eureka should be possible to enable/disable in unit-tests via an annotation.