4 ms·
> To know the difference between SRE and DevOps ask them what they do when an incident happens: > DevOps rolls back (reverts the changes, treating th
by beaviskhan 3y ago
> To know the difference between SRE and DevOps ask them what they do when an incident happens:
> DevOps rolls back (reverts the changes, treating the system as a black box that should go to the last known good state)
> SRE fixes forward (fixes the problem and commits a new change)
Ehhhh. I don't think it's that simple, and you'd better know what your strategy is for incident response BEFORE one happens. By far the worst shitshows I've seen in production have been as a result of well-intentioned people trying to fix forward without fully understanding what is going on.
Spoiler: having full understanding of what is going on in the heat of the moment is really, really hard, even for smart people who are also system experts. Rolling back as a default and then figuring out what went wrong in a more orderly manner is a perfectly sensible default behavior where such a thing is possible.
- gurchik 3y agoI also took issue to this, but it looks like the author responded in a comment. If I understand their intentions correctly, it probably would be better phrased as: "if rolling forward isn't even considered, it's DevOps, otherwise it's SRE." While I can't disagree with the author's experience, in my experience the title is meaningless. At my current job some coworkers think I'm an SRE, some people think I'm DevOps, and some people think I'm in IT.
- sanderjd 3y agoI would say that the best SREs I've worked with do the immediate revert for all these reasons, but also can and frequently do implement the fix :) (But I'd say that's also true of DevOps people I've worked with, so not sure the differentiation makes much sense...)