Yeah! Or the team there prioritizes taking care of folks and maintaining boundaries between work and life by having that 3 hours of downtime during normal business hours.
Would love to hear other stories of businesses doing similar activities during sane weekday hours.
“Do it during the day without an outage.” is my approach.
It requires specific technology choices and planning ahead, but it is especially simple in the web era because they all go through load balancers which are redundant themselves.
The opposite example was Blizzard taking down WoW for half a day every week, which is an absurdly long time.
Even if they had a single server per game world instance, they could have orchestrated updates using automation to take each instance down for a few minutes instead of all of them at once for many hours.
At my previous company (a Fortune 20) when I controlled maintenance for my applications...I scheduled it during the day because there is more resources if things screwed up. Rolling maintenance meant 0 down time, even if unsuccessful.
Maybe their largest market is Europe? Or they make enough money that their engineers don't want to work late hours.
Yeah! Or the team there prioritizes taking care of folks and maintaining boundaries between work and life by having that 3 hours of downtime during normal business hours.
Would love to hear other stories of businesses doing similar activities during sane weekday hours.
“Do it during the day without an outage.” is my approach.
It requires specific technology choices and planning ahead, but it is especially simple in the web era because they all go through load balancers which are redundant themselves.
The opposite example was Blizzard taking down WoW for half a day every week, which is an absurdly long time.
Even if they had a single server per game world instance, they could have orchestrated updates using automation to take each instance down for a few minutes instead of all of them at once for many hours.
1 reply →
At my previous company (a Fortune 20) when I controlled maintenance for my applications...I scheduled it during the day because there is more resources if things screwed up. Rolling maintenance meant 0 down time, even if unsuccessful.
Are you implying that's a bad time? What time would you pick?
Steam is under heavy use at all times, and the lowest user count is roughly from 3PM-2AM PST.
And being partially off for 3 hours a week is pretty far from "business hours".
If I was steam I think I’d find a way to have zero downtime deployments. A/B or whatever