Site Reliability Engineering (SRE) in the old-school kindergarten

Middle School

Elementary School

Figure 1. Dev, Ops, and DevOps.
Figure 2. Dev, Ops, DevOps, and SRE.

Kindergarten — Takeaways

  1. Allocate reliability requirements and concerns in a dedicated team, the SRE team;
  2. Use simple apparatus to handle reliability, namely SLO, error budget, and SLI;
  3. Use error budget to enact the capacity to influence the direction of the given organization, process, and product by the four teams, namely DEV, OPS, DEVOPS, and SRE. Recall the direction of the forces exerted by each team.

References

--

--

--

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Back To Basics

Libary

What to expect from Launch School’s RB109 Written Assessment

What You Missed At MindSea’s Last Mobile Hackathon!

Configure a vpn server on Linux (Ubuntu 16.04) EC2 instance

Using Hash Tables

Hackish Way to Capture Traffic of ‘XMPP’(i.e. non-HTTP protocols ) of Mobile Applications.

OOP Design & Analysis With BookStore Management — Part I

Free(dom inducing) Public JSON APIs…

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Alessandro Gerlinger Romero

Alessandro Gerlinger Romero

More from Medium

How Defining Code Owners Can Radically Improve Your Code Reviews

Containerized software vendor principles

Site Reliability Engineering: Setting up the right Monitoring System

Dealing with data in microservice architectures