Honestly, I don't aim for zero downtime deploys. I simply don't care if I have a few seconds of possible service interruption during a deploy. If I did, I'd ke

Honestly, I don't aim for zero downtime deploys. I simply don't care if I have a few seconds of possible service interruption during a deploy. If I did, I'd keep it simple. I use Nginx in front of the Go server. I'd likely use the Nginx server as a load balancer and replace each Go service one at a time to have no downtime. It doesn't matter how many ports you use as long as Nginx knows the port range. It will distribute the incoming requests to the Go processes. edit: For those wondering why I use Nginx. It's where I terminate SSL and I also use it for simple gzip/compression/caching for outgoing resources. I don't use Caddy or anything else. I've used Nginx for many years and it just... works.