DevOps vs SRE
What I've learnt so far
@CarolSaysThings
About me
@CarolSaysThings
System Administrator
DevOps Engineer
SRE Engineer
?
@CarolSaysThings
What is DevOps?
It is not a position or a team.
It is a movement.
It is a culture.
@CarolSaysThings
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.
@CarolSaysThings
DevOps is underpinned by three principles, called the 3 ways
@CarolSaysThings
The first way
Systems Thinking
@CarolSaysThings
The second way
Amplify feedback loops
@CarolSaysThings
The third way
Culture of continuous experimentation and learning
@CarolSaysThings
What is SRE?
Fundamentally, it’s what happens when you ask a software engineer to design an operations function.
@CarolSaysThings
Let's have a look at some of the core concepts of SRE
@CarolSaysThings
SLO
1. Knowing what your normal looks like
2. Defining an appropriate level of reliability (SLO)
3. Bridge the gaps/optimise
@CarolSaysThings
Error budgets
Stabilising the system
Intentionally destabilising the system
Releasing features
@CarolSaysThings
Toil
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
@CarolSaysThings
While they're different sets of ideas, each movement enables and complements the other
@CarolSaysThings
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
@CarolSaysThings
Conclusion
DevOps is a culture, while SRE is a way of handling operations
They share many objectives
You should find what works for you 🙂
@CarolSaysThings
Thank you!
@CarolSaysThings
Further Reading
@CarolSaysThings