I've released the latest .NET API too for the dozens of us that use .NET with Consul. It features full (.NETStandard 1.3) support of Core in this version! https://www.nuget.org/packages/Consul/0.7.0
Consul 0.7
11–20 of 22 posts
Re: Consul 0.7
#12Wish they would fix the issue with the watch triggers.
Re: Consul 0.7
#13Has anyone upgraded from 0.6.x yet? Care to share your experience?
Re: Consul 0.7
#14Consul combined with consul-template for dynamic config changes in your environment is an extremely powerful solution which just works with minimum fuss. Works well when deploying clusters such as zookeeper, allows all the nodes to discover each other automatically and work out their id number.
I am curious, why you are using both ZK and Consul as there is much overlap there.
Re: Consul 0.7
#15Thanks for some great tools guys, and a shout out to Fabio another great tool built on top of Consul https://github.com/eBay/fabio
How does Fabio handle being a single point of failure?
Re: Consul 0.7
#16Thanks for some great tools guys, and a shout out to Fabio another great tool built on top of Consul https://github.com/eBay/fabio
How does Fabio handle being a single point of failure?
This might be naiveté on my part, but I would assume you run multiple Fabio instances and treat it like you would any other LB.
Do you mean something else by your question?
Re: Consul 0.7
#17Thanks for some great tools guys, and a shout out to Fabio another great tool built on top of Consul https://github.com/eBay/fabio
How does Fabio handle being a single point of failure?
You can run Fabio alongside the Consul agent on each node in your cluster and point all your apps to localhost:9999. That way you don't have to manage a central cluster of Fabio instances and if a node dies you just lose the Fabio instance on that host, which was only being used by that host.
Re: Consul 0.7
#18Consul combined with consul-template for dynamic config changes in your environment is an extremely powerful solution which just works with minimum fuss. Works well when deploying clusters such as zookeeper, allows all the nodes to discover each other automatically and work out their id number.
I am curious, why you are using both ZK and Consul as there is much overlap there.
There's lots of software you might operate that requires zookeeper: kafka, solrcloud, the hadoop ecosystem, etc.
Meanwhile, consul has lots of functionality built in that makes it a snap to use for service discovery within your existing infrastructure. You would have to build all this yourself on top of zookeeper, which just provides a distributed, consistent key-value store.
So it's easy to see why you could end up with both.
Re: Consul 0.7
#19Earlier quoted context omitted.
How does Fabio handle being a single point of failure?
This might be naiveté on my part, but I would assume you run multiple Fabio instances and treat it like you would any other LB. Do you mean something else by your question?
Yes I meant something different. Generally with a load balancer the load balancer hosts that VIP(s) that your public facing DNS A records resolve to. In order to avoid a single point of failure you employ things like keepalived or ECMP/BGP etc.
Re: Consul 0.7
#20The new Lifeguard feature looks really neat. False monitoring alarms are a big issue. If they happen a lot you begin to not trust a real alarm and ignore them - the boy who cried wolf as the cliche goes.