DevOps or SRE

Are DevOps and Site Reliability Engineers competitors or a tandem that perfectly complement each other?

Let’s find it out.

Site Reliability Engineers (SRE) solves operationally scaling, and reliability issues. SRE’s focus is on system stability.

The fundamental principles of SRE include:

• Creating CI/CD DevOps processes to automate infrastructure scaling,
• Devoting at least 50% of the time to improving the system, not to routine tasks;
• Creating a Service Level Agreement, Service Level Objectives, and Service Level Indicators for your services and measuring system performance against them,
• Setting up an error budget to control the rate at which the changes are introduced into production,
• Implementing in-depth monitoring to see latency, congestion, traffic, and errors,
• Writing response scripts to address issues based on clear symptom-based alerts and
• Correcting any errors found

In turn, DevOps is a set of cultural principles, approaches, and tools that improve the ability of companies to build applications and services at high speed. I​​ts main principles are similar to those of SRE, but its focus is much wider.

There are five key pillars of DevOps namely:

• No more silos as the absence of cooperation and information flow between teams decrease performance,
• Failure is okay as DevOps dictate learning from mistakes, and not wasting resources on an unreachable purpose,
• The change must be progressive as changes are most efficient and less risky when they are tiny and regular,
• The more automation, the better as DevOps concentrates on automation to provide upgrades faster and save hours of monotonous work and
• Metrics are crucial as every change should be measured to see if it delivers the desired results

So how does SRE relate to DevOps? Watch this video till the end to find out.

Don’t forget to give us your 👏 !

Wanna keep in touch online? Twitter | Facebook | Instagram