diplomat

I got really excited about Consul when I read about it here many years ago. I wrote a ruby library for it (https://github.com/WeAreFarmGeek/diplomat) which became rather popular, and was used by quite a few large organisations. Hashicorp sent me a care package to thank me - a T-shirt and a card signed by Mitchell himself - I wore that T-Shirt until it was threadbare and I still have the card. Its a small thing on the grand scale of things, but it's something I look back on with pride. Well done to the Hashicorp team for getting to where they are now - by building something new and useful, and by fundamentally not being greedy.

Both Diplomat (github.com/wearefarmgeek/diplomat) and Postie (https://github.com/johnhamelink/postie) are looking for logos.

Works great. We have several services (rails and Python) that use consul in AWS for service discovery and as a shared key/value store for some types of configuration. You could do the service discovery part with tags, and use S3 or dynamo db for the config part instead of using consul. Since we develop locally on a small collection of VMs we prefer consul instead (no aws tags on our local vagrant VMs!). Check out the diplomat gem (https://github.com/WeAreFarmGeek/diplomat) and these others for Python: - https://github.com/cablehead/python-consul - https://github.com/gmr/consulate

I can't speak for zookeeper, but I've been using consul in production since 1.0. I've never had an issue with it - it works great for me! I've written a ruby gem to interface with it's API called Diplomat (here: https://github.com/WeAreFarmGeek/diplomat) and a whole bunch of ansible scripts to setup checks for postgres, nginx, etc.