DevOps primarily focuses on Delivery Speed and SRE focuses on Reliability in production but where does Production Support Engineers fit who also focuses on production monitoring, alerting, performance, user experience, incident management, RCA and work on code defects and understand business functionality?

  • In a SRE world, would production support engineers be more aligned to SRE or merged with SRE?
  • In a SRE world, would production support engineers be more aligned to SRE or merged with SRE? - PS engineers would merge with SRE. – KatariaA Mar 26 at 2:26

The best answer to DevOps vs SRE is here What's the Difference Between DevOps and SRE ? From the above series, you will understand Class SRE implements DevOps and both are working on a similar ground and it's pretty align goal for both of them.

As a production support, you will be doing the task which you have mentioned in the question, apart, you need deep visibility, alert and notifications, latency, metrics, tracking, security, etc. lots of things to take care. And, it basically providing the service to the end users who is utilizing your application or system. Also, I see production support team have written the dockerfile and bash scripts to automate many tasks. So, whenever user faced any issue that first comes to Production Support team and it might went to other IT teams if it's not easily resolve. But, if you look at SRE, their sole purpose is to keep system in reliable state every time, maintain resiliency, etc. In some organization, the DevOps does this part too.

From my perspective, all the three terms are same as their goal align and just differ in functionality. These functionality differs from organization to organizations. But, DevOps are intended to bring culture and shift in paradigm so that everyone will work collaboratively. Hope this helps.


I don't want to nit pick, but I respectfully disagree with the idea that DevOps is about speed while SRE is about reliability. I understand this is an easy thing to think -- especially because SRE has "Reliability" in its name -- but it a'int so. :-)

SRE is all about velocity.

We think that over the long run you'll go much much faster if you recognize when the wheels are starting to go wobbly (SLOs and Error Budgets) and slow down in those cases to make things better. That, in our experience, is much faster than having to stop for a goodly long time because we let a bunch of reliability related technical debt pile up.

SRE can be thought of as a specific instantiation of DevOps with a more uniformly enforced set of constraints. (Hence the Class SRE implements DevOps formulation above.)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.