Zero Downtime Frontend Deploys with Vulcand on CoreOS

The architecture is sound. But half-assing a loadbalancer impl (vulcand) instead of embedding HAProxy is a terrible idea.

We have something very similar at Balanced called Rump (routing umpire). It&#x27;s written in python has a pretty cool rule based engine and a swappable backend.<p>It currently uses ZK and Chef, but it would be pretty interesting to use something like Etcd&#x2F;Consul since no one wants to maintain a ZK cluster.<p>If there are individuals who want to hack on it, shoot me a msg on twitter and I&#x27;ll see what I can do to speed up the process to open source it.

What great timing! I was just about to roll my own using etcd, haproxy and a bunch of perl duct tape.<p>Very excited to take a good look at vulcand.

Top notch technical writeup. We&#x27;ve had our eyes on Vulcand for some time now, though we&#x27;d really like to see native TCP support.

I&#x27;ll ask about the reasoning instead of attacking the decision (since that didn&#x27;t get a response).<p>Why not embed HAProxy?

etcd, fleet, deis, and now this are getting me more and more tempted to move from Velociraptor to the Docker ecosystem.<p>If Deis could run my uptests[0] before Vulcan gets called to re-route things, that&#x27;d be awesome.<p><a href="https://bitbucket.org/yougov/velociraptor/src/2bcef54253a9e9238aee92de92b6d088a5d33c60/docs/uptests.rst" rel="nofollow">https:&#x2F;&#x2F;bitbucket.org&#x2F;yougov&#x2F;velociraptor&#x2F;src&#x2F;2bcef54253a9e9...</a>

This is a golang project, no?