Consul vs Keepalived: What are the differences?
Consul: A tool for service discovery, monitoring and configuration. Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable; Keepalived: A routing software written in C. The main goal of this project is to provide simple and robust facilities for loadbalancing and high-availability to Linux system and Linux based infrastructures.
Consul and Keepalived can be primarily classified as "Open Source Service Discovery" tools.
Consul is an open source tool with 16.8K GitHub stars and 2.92K GitHub forks. Here's a link to Consul's open source repository on GitHub.
According to the StackShare community, Consul has a broader approval, being mentioned in 186 company stacks & 339 developers stacks; compared to Keepalived, which is listed in 3 company stacks and 8 developer stacks.
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 Keepalived?
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