DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’» is a community of 963,274 amazing developers

We're a place where coders share, stay up-to-date and grow their careers.

Create account Log in
Rebecca
Rebecca

Posted on

SRE vs DevOps

We often hear SRE and DevOps interchangeably used to describe operational activities done by engineers for applications running in private or public cloud environments. What’s the difference?

From Wikipedia
β€œDevOps is a set of practices that combines software development (Dev) and IT operations (Ops).”
β€œSite reliability engineering (SRE) is a set of principles and practices[1] that incorporates aspects of software engineering and applies them to infrastructure and operations problems.[2]
DevOps was coined by Patrick Debois in 2009 to describe the culture of having developers and operations engineers work together. There was a constant conflict between developers who build the software and IT operations teams that manage the day to day operations of the software. It was often referred to as developers throwing software β€œover the wall” to operations.

DevOps brought a change to this culture that brings the responsibility of building and running software to both dev and ops, with increasing collaboration and shared responsibility across various aspects of software development life cycle (code, build, test, deploy and management)
β€œDevOps is not a process or a technology. It’s a philosophy or culture of having developers and operations work together to achieve the common goal of running software to achieve high performance and high availability.”

The field of site reliability engineering (SRE) originated at Google with Ben Treynor Sloss, who founded a site reliability team after joining the company in 2003. The Google SRE books have formalized many of the ideas that are developed in these site reliability teams since then.

Unlike DevOps, SRE is both a job function and a set of principles that are followed by a team to achieve high reliability for software services offered by a company to its customers. SRE also brought engineering principles of writing β€œinfrastructure-as-code”, testing and deploying operational software similar to how product services are developed.
β€œSREs are software engineers doing operational work!”
Though SRE predates DevOps, it’s an implementation of DevOps principles in a specific manner. Automation plays an important role in SRE.

For an in-depth explanation of β€œWhat’s SRE”, check out our other blog on www.Fylamynt.com
Fylamynt is an SRE platform that helps SREs build and run automation workflows.

Top comments (0)

Take a look at this:

Settings

Go to your customization settings to nudge your home feed to show content more relevant to your developer experience level. πŸ›