Thanks brianwawok, I'm currently experimenting with #1, switching between two batches of docker containers with a bunch of script, but am curious about is there more robust approaches to this? What are people using professionally in real world?
The real world is a huge range. In my experience, something like 75% of the world does..
1) Push out a new code
2) Shut down all prod servers at once
3) Restart them
Maybe during a weekly maintenance window.. maybe at 2am.. maybe at noon.. depending on the company and clients. Basic assumption is "Meh, people will reload if the page is down for a few minutes"
Even though 0 downtime is the "right" way to do stuff, seems like the ops level of many places is not that high.
The fact that you have scripts and are making some kind of attempt for less downtime puts you in the top 25% of the internet.
Comments
Thanks brianwawok, I'm currently experimenting with #1, switching between two batches of docker containers with a bunch of script, but am curious about is there more robust approaches to this? What are people using professionally in real world?
The real world is a huge range. In my experience, something like 75% of the world does..
1) Push out a new code
2) Shut down all prod servers at once
3) Restart them
Maybe during a weekly maintenance window.. maybe at 2am.. maybe at noon.. depending on the company and clients. Basic assumption is "Meh, people will reload if the page is down for a few minutes"
Even though 0 downtime is the "right" way to do stuff, seems like the ops level of many places is not that high.
The fact that you have scripts and are making some kind of attempt for less downtime puts you in the top 25% of the internet.