Registered services and nodes can be queried using both a DNS interface as well as an HTTP interface.
This is very cool. Integrating with a name resolution protocol that every existing programmer and stack knows how to use (often without even thinking about it) should lead to some magical "just works" moments.
IIRC, the Chubby paper mentions how Google put protocol conversion servers in front of Chubby to convert DNS queries into lookups into a Chubby cluster. Here, it's built right into the service itself.
Comments
Registered services and nodes can be queried using both a DNS interface as well as an HTTP interface.
This is very cool. Integrating with a name resolution protocol that every existing programmer and stack knows how to use (often without even thinking about it) should lead to some magical "just works" moments.
See also SkyDNS, another service discovery system: http://blog.gopheracademy.com/skydns
In common with Consul:
* DNS interface
* Operates as a distributed cluster
* Uses Raft for consensus
SkyDNS is compared to Consul here: http://www.consul.io/intro/vs/skydns.html
IIRC, the Chubby paper mentions how Google put protocol conversion servers in front of Chubby to convert DNS queries into lookups into a Chubby cluster. Here, it's built right into the service itself.