3 ms·
When you deploy a new version of a container, how do you avoid downtime? Do you start a new container running the new version, wait for the new container to be
by ngrilly 8y ago
When you deploy a new version of a container, how do you avoid downtime? Do you start a new container running the new version, wait for the new container to be ready, switch traffic to the new container, stop traffic to the old container and drain connections, and then stop the old container?
- vidarh 8y agoFor my home projects it doesn't matter. For work projects, yes. It's an easy thing to automate. Incidentally most of the pain in this is that most load balancers are reverse of what makes most sense: the app servers ought to connect to the load balancer and tell it when it can service more requests, not get things pushed at it.
- ngrilly 8y ago> most load balancers are reverse of what makes most sense: the app servers ought to connect to the load balancer and tell it when it can service more requests, not get things pushed at it Reminds me of Mongrel2
- vidarh 8y agoYes, Mongrel2 is an interesting design. So many things get simpler when you invert that relationship.