DevOps vs SRE

What I've learnt so far


About me


System Administrator

DevOps Engineer

SRE Engineer



What is DevOps?

It is not a position or a team.

It is a movement.

It is a culture.


DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support.


DevOps is underpinned by three principles, called the 3 ways


The first way

Systems Thinking


The second way

Amplify feedback loops


The third way

 Culture of continuous experimentation and learning


What is SRE?

Fundamentally, itโ€™s what happens when you ask a software engineer to design an operations function.


Let's have a look at some of the core concepts of SRE



1. Knowing what your normal looks like

2. Defining an appropriate level of reliability (SLO)

3. Bridge the gaps/optimise


Error budgets

Stabilising the system

Intentionally destabilising the system

Releasing features



Work that is manual, repetitive, automatable, has no enduring value

Google caps it at 50%

Rest of time spent on engineering work that reduces future toil or adds features


While they're different sets of ideas, each movement enables and complements the other


Both movements promote cooperation between Dev and Ops

They seek automation and experimentation

Monitoring and eliminating toil - 1st way

Error budgets allow us to be experimental - 3rd way

Blameless post-mortems - 2nd way



DevOps is a culture, while SRE is a way of handling operations

They share many objectives 

You should find what works for you ๐Ÿ™‚


Thank you!


Further Reading