3 ms·

Thank you for the detailed response. It's a good outcome that the sacrifices of systems teams are more widely recognized in your company now; at many companies

Thank you for the detailed response. It's a good outcome that the sacrifices of systems teams are more widely recognized in your company now; at many companies they are not. Online maintenance is how we do all our maintenance. Getting to that point as early as possible is essential for redundancy and failover, anyway, so it is both good for the company and good for the systems team.

sokoloff 13y ago
Online maintenance is huge, and it's somewhat easier to design for now than it was 10 years ago. It's very nice to be able to schedule releases at a human/humane time and there's really only one point in our release process now where it's impossible to very obviously and fairly automatically revert and regroup. That one point is clearly called out, and the decision is easy to make when the site has been operating on live traffic for 60 minutes with zero perceptible technical and business metrics degradation. I'd not consider online maint capability to be a necessary part of an MVP, since any time you spend on it is unlikely to help you understand whether you even HAVE a business, but I'd prioritize it pretty highly in the very next phase of company development.