I run 3 websites written in Go (http://blog.kowalczyk.info/article/uvw2/Thoughts-on-Go-after...)

Those are clearly not Facebook scale servers but for majority of people: you don't need this or any other such solution.

Here's what I do for deployment. I have a fabric script that:

- copies the new executable to the server - kills currently running executable - starts the new executable

The worst that can happen is that a few connections will get dropped and that's perfectly fine 99.9% of websites. You don't control internet so the users will get broken connections all the time for reasons you can't eliminate. They shrug and hit reload button.

Complicating things to avoid few seconds of downtime was not worth it for me and rationally, probably not worth it for most.