3 ms·
Flynn isn't a service discovery library by itself. It's more of a self hosted Heroku. Though, it does use etcd for service discovery.
by andrewmunsell 13y ago
Flynn isn't a service discovery library by itself. It's more of a self hosted Heroku. Though, it does use etcd for service discovery.
- dominotw 13y agoAre you sure flynn uses etcd for service discovery instead of its own[1]? Looks like it uses Google Omega instead of RAFT which etcd uses. https://github.com/flynn/discoverd https://github.com/flynn/discoverd
- andrewmunsell 13y agoYou can read more about service discovery on the Flynn site: https://flynn.io/docs/architecture#service-discovery https://flynn.io/docs/architecture#service-discovery discoverd is an API on top of another system. Right now, Flynn uses discoverd backed by etcd, though they indicate that this could be replaced with Zookeeper, etc. due to the mdoular design.
- thu 13y agoVery first line of discoverd's README: It's currently backed by etcd[...]
- dominotw 13y agototally missed that. thank you.
- nemothekid 13y agoAs I understand it Google Omega and RAFT are two different things. Google Omega is Google's answer to Apache Mesos. Omega would need a service like Raft to understand what services are currently available. In short, Google Omega is not a service discovery service.
- hendzen 13y agoActually, I think Google Omega is the next-generation scheduler after their original Borg scheduler, which in-turn inspired Mesos. The design of Omega is quite different than Mesos. I really do recommend reading the Mesos & Omega papers, they are quite interesting. And yes, Raft is a consensus algorithm for keeping a set of distributed state machines in a consistent state. Mesos actually uses ZooKeeper under the hood for master election, which uses its own consensus algorithm (ZAB - Zookeeper Atomic Broadcast).