etcd vs SkyDNS: What are the differences?
etcd: A distributed consistent key-value store for shared configuration and service discovery. 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; SkyDNS: Distributed service for announcement and discovery of services. 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).
etcd and SkyDNS can be categorized as "Open Source Service Discovery" tools.
etcd and SkyDNS are both open source tools. It seems that etcd with 25.5K GitHub stars and 5.18K forks on GitHub has more adoption than SkyDNS with 1.96K GitHub stars and 302 GitHub forks.
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.