DevOps Vs. SRE: The Productivity Conundrum
-
Loading... - Aubin Kandem
- 03 Oct 2022
- 78 Views
- 0 Like
- 0 Comment
Within the realm of software development, two related ideas known as “DevOps” and “Site Reliability Engineering” (SRE) have been coexisting for more than a decade now. It’s possible that they could be considered rival businesses at first glance. However, a closer look reveals that the apparent competitors are, in reality, pieces of a puzzle that complement and fit together nicely.
This article explains how DevOps and SRE make it easier to develop reliable software, where the two practices overlap, how they are distinct, and when they can most effectively work together.
A Comparison between SRE and DevOps
Two distinct methodologies aim to achieve the same result: to close the gap between the development and operations teams. Both initiatives seek to shorten the release cycle and enhance the product’s reliability. But before we delve any further into the distinctions and parallels that exist between the two, let’s take a step back and consider when and why SRE and DevOps came into existence in the first place.
What is SRE?
Site Reliability Engineering, also known as SRE, is an innovative method of approaching information technology operations that puts software first and is supported by a set of corresponding practices. It was developed at Google in the early 2000s to monitor the overall health of a large and complex system that handled more than 100 billion requests daily.
The elements that contribute to the reliability are presented in the form of a pyramid below. The elements range from the most fundamental (monitoring) to the most sophisticated (reliable product launches). Read More...
