3 ms·
Wonder how this compare to Smart Stack: http://nerds.airbnb.com/smartstack-service-discovery-cloud/ http://nerds.airbnb.com/smartstack-service-discovery-cloud/
by jakozaur 12y ago
Wonder how this compare to Smart Stack:
http://nerds.airbnb.com/smartstack-service-discovery-cloud/ http://nerds.airbnb.com/smartstack-service-discovery-cloud/
E.g. you got webservices talking over HTTP. One goes bad, you want existing clients not to talk to them.
Smart Stack: you are using HTTP proxy on each machine. You're code doesn't has to be aware of who is talking to.
Consul: Not sure, but it sounds like server code has to be able to handle events to change that.
- burnout1540 12y agoSome more info here: https://consul.io/intro/vs/smartstack.html https://consul.io/intro/vs/smartstack.html
- tigeba 12y agoConsul provides service discovery via a REST API and via DNS. I had to make some small configuration and code changes to my existing services to make use of SRV records. They have no knowledge of Consul's existence.
- armon 12y agoWe compare Consul to SmartStack here: https://www.consul.io/intro/vs/smartstack.html https://www.consul.io/intro/vs/smartstack.html With a tool like consul-template, you can have the same behavior that Synapse gives you. https://hashicorp.com/blog/introducing-consul-template.html https://hashicorp.com/blog/introducing-consul-template.html In the general case, clients of Consul don't need special handling code for events, it's handled by Consul for you.
- kilburn 12y agoAs far as I understand, the less involved method is: Consul: your calling webservice uses a DNS name served by consul. Consul responds with a pool of working servers. As soon as one fails, consul doesn't include its address anymore, and hence the calling services stop talking to it.