3 ms·
You don't even need containers--it's a feature of load balancers containers rely on. Start new container, wait for it to become healthy, add it to the load bala
by nijave 7y ago
You don't even need containers--it's a feature of load balancers containers rely on. Start new container, wait for it to become healthy, add it to the load balancer, remove old container (with an optional, let connections to old container close first)
- PunchTornado 7y agowhat if it involves db updates?
- rblatz 7y agoWhere I work we had that same thought. Until we stopped doing breaking database changes.
- sethammons 7y agoWe have run a lot of db changes. It requires multiple steps. Add a column, migrate data, update code to use new column and old column, update code to use only the new column, update table to drop old column. Similar for migrating to new dbs, tables, etc. It is rare for us to need to disable writes for a version bump or something.