Live data from Hacker News

Service Discovery with Mesos-DNS

mesosphere.com

11–13 of 13 posts

Re: Service Discovery with Mesos-DNS

#11
post #9

I haven't yet had a chance to play with or research Mesosphere, but I'm hearing it mentioned more and more. Are its goals similar to that of CoreOS and/or Docker Swarm, in that we're slinging around services/containers rather than managing machines or VMs?

A quick summary of what Mesosphere is working (DCOS - the datacenter opearting system) on is at https://mesosphere.com/ .

Apache Mesos, the core of Mesosphere's infrastructure, has been in use by companies like Twitter for years to manage clusters with 10s of thousands of servers. http://mesos.apache.org/

Re: Service Discovery with Mesos-DNS

#12

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.

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.

Re: Service Discovery with Mesos-DNS

#13
post #2

Doesn't this sound a lot like DNS-SD over mDNS?

I think it's centralised, so you don't need to either have all your machines on one subnet or configure your routers (if you can) to forward DNS-SD packets between all your subnets, probably creating a small broadcast storm at scale.

DNS-SD doesn't require mDNS, you can use it with generic DNS servers. There's an example in the RFC, see https://tools.ietf.org/html/rfc6763#section-13.1

But it's usually used with mDNS on a local network.

Post reply on HN