Consul

875
1K
+ 1
198
CoreDNS

24
34
+ 1
4
Add tool

Consul vs CoreDNS: 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; CoreDNS: DNS and Service Discovery. CoreDNS is a DNS server. It is written in Go. It can be used in a multitude of environments because of its flexibility.

Consul belongs to "Open Source Service Discovery" category of the tech stack, while CoreDNS can be primarily classified under "DNS Management".

Some of the features offered by Consul are:

  • Service Discovery - Consul makes it simple for services to register themselves and to discover other services via a DNS or HTTP interface. External services such as SaaS providers can be registered as well.
  • Health Checking - Health Checking enables Consul to quickly alert operators about any issues in a cluster. The integration with service discovery prevents routing traffic to unhealthy hosts and enables service level circuit breakers.
  • Key/Value Storage - A flexible key/value store enables storing dynamic configuration, feature flagging, coordination, leader election and more. The simple HTTP API makes it easy to use anywhere.

On the other hand, CoreDNS provides the following key features:

  • Plugins
  • Service Discovery
  • Fast and Flexible

Consul and CoreDNS are both open source tools. It seems that Consul with 16.4K GitHub stars and 2.85K forks on GitHub has more adoption than CoreDNS with 4.32K GitHub stars and 695 GitHub forks.

Advice on Consul and CoreDNS
Needs advice
on
Eureka
etcd
and
Consul
in

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.

See more
Pros of Consul
Pros of CoreDNS

Sign up to add or upvote prosMake informed product decisions

Sign up to add or upvote consMake informed product decisions

What is Consul?

Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable.

What is CoreDNS?

CoreDNS is a DNS server. It is written in Go. It can be used in a multitude of environments because of its flexibility
What companies use Consul?
What companies use CoreDNS?

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Consul?
What tools integrate with CoreDNS?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Consul and CoreDNS?
etcd
etcd is a distributed key value store that provides a reliable way to store data across a cluster of machines. It’s open-source and available on GitHub. etcd gracefully handles master elections during network partitions and will tolerate machine failure, including the master.
Zookeeper
A centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications.
SkyDNS
SkyDNS is a distributed service for announcement and discovery of services. It leverages Raft for high-availability and consensus, and utilizes DNS queries to discover available services. This is done by leveraging SRV records in DNS, with special meaning given to subdomains, priorities and weights (more info here: http://blog.gopheracademy.com/skydns).
Ambassador
Map services to arbitrary URLs in a single, declarative YAML file. Configure routes with CORS support, circuit breakers, timeouts, and more. Replace your Kubernetes ingress controller. Route gRPC, WebSockets, or HTTP.
Kubernetes
Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
See all alternatives
Interest over time
News about CoreDNS
More news