Consul vs Eureka vs Zookeeper: What are the differences?
Consul is a service discovery framework with a REST interface and some features such as health checking, service segmentation with its own internal distributed key-value store. Consul includes service discovery, but also rich health checking, locking, Key/value, multi-datacenter federation, an event system. Eureka – A service discovery tool, the architecture is primarily client/server, with clients mainly using embedded SDK to register and discover services. A service locator used as part of Netflix's load balancers and failovers. Zookeeper –Apache Zookeeper is a distributed key-value store which can be used as the basis to implement service discovery. Mostly a common-purpose distributed key/value store used for service-discovery in conjunction.
Breaking a monolith into microservices and handling the scaling and health of new services as they come only. This should ideally help to reduce the overhead needed to get a service online. We have all of this being handled by custom URLs and health checks being done at the expense of infrastructure setup time and maintenance (VM sprawl). Initially, I am looking at Consul for the TLS proxy and security options as well as the KV store which may prove useful in cross datacenter environments.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Consul?
What is Eureka?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions