Re:Service Discovery with Mesos-DNS
by preillyme on Wednesday January 21, 2015 @10:51AM
(#8923576)
Awesome, Mesos-DNS is simple and stateless. Unlike Consul and SkyDNS, it does not require consensus mechanisms, persistent storage, or a replicated log. This is possible because Mesos-DNS does not implement heartbeats, health monitoring, or lifetime management for applications. This functionality is already available by the Mesos master, slaves, and frameworks.
[ Parent
| on HN ]
The same is the case for SkyDNS2. It runs just fine against our Etcd backends.
In both cases the combination (SkyDNS + Etcd or Consul) looks far less complicated than Mesos, so I don't really see what you think you gain. If you already have other reasons to want to run Mesos, sure.
They are simpler but keep it mind all the other things you get from running on Mesos, like provisioning your services, having your services restarted when they crash, workload migration when machines fail, bin-packing so you don't waste resources, etc.
This is great if you're "all in" on Mesos. However the advantages to a truly independent service discovery system (such as Consul etc.) are that it:
* Doesn't tie you to Mesos, as it can move to another "datacenter OS" along with your software.
* Allows you to mix software-on-Mesos with software that's not.