SRE & DevOps - BFFs
DevOps and SRE are friends, not foes. SRE is the concrete implementation of DevOps. We can think of DevOps as the What and SRE as the How.
In other words, SRE is a prescribed set of practices that we can use to build our capabilities in the various DevOps areas.
“If you think of DevOps like an interface in a programming language, class SRE implements DevOps” – Google
SRE was started by Google in the early 2000s independently from the DevOps movement that began in 2008 with Andrew Clay and Patrick Debois. It just so happens that SRE embodies the DevOps philosophies and provides a set of engineering and operation practices for measuring and achieving reliability.
The relationship between SRE practices and DevOps philosophies can be thought of as follows:
SRE has a clearly defined set of expectations and practices for meeting those expectations, whereas DevOps is much more abstract, with the definition and practices varying from organisation to organisation.
We can consider SRE and DevOps as BFFs that work hand in hand to help bring development and operation teams closer together through shared responsibility, a common goal of enabling automation and increasing reliability.
Founder/Engineer @ Genai | DevOps, SRE, AI
3 年SRE and DevOps have quite a special relationship and both look to achieve similar goals all be it from different angles. I think this sums them up quite succinctly: (Google's words) "DevOps has emerged as a culture and a set of practices that aims to reduce the gaps between development and software operation" "SRE defines the overall behavior of the system, with the implementation details being left up to the author"
(Azure + D365) + (Agile + DevOps) = Operational Efficiency
3 年Nice post Keith Jenneke. Thanks for sharing!