3 ms·
It's also interesting how U.S.-centric this thinking is: your sneaky 3am deploy in the valley could mean a mid-morning outage in London. Actually, an 8am deplo
by hopeless 15y ago
It's also interesting how U.S.-centric this thinking is: your sneaky 3am deploy in the valley could mean a mid-morning outage in London.
Actually, an 8am deployment in Europe has the advantages of a rested brain and a few hours before America hammers the Internet ;-)
- virmundi 15y agoMany US based software companies either A) have a mostly American user base or B) have a regional distribution setup for their app. So if you are a non-American in camp A, that is a problem for you. However, remember the goal is to be the least disruptive. If you are a non-American in a region that the server is deployed in, there is probably a night-based take down of the system in your region. If the software company is either A nor B, then the software company need to notify the non-user users that they may experience a disruption.
- mseebach 15y ago> Actually, an 8am deployment in Europe has the advantages of a rested brain and a few hours before America hammers the Internet ;-) And the disadvantage of happening in the middle of mainland Europe morning rush. I think the point is that you take the downtime when it's least disruptive to your users, who/wherever they might be.