Much That We Have Gotten Wrong About SRE
An illustrated summary of Developers ➡ DevOps ➡ SRE
Much That We Have Gotten Wrong About SRE

1. Developers wanted to ship their produce

To the other side

2. Production never matches the development environment. It resembles, but cannot match

So they deployed people on the other side

3. But this process was slow, they wanted to deploy faster

So they deployed Continuous-Deployment (CI/CD)

4. To improve reliability, we got SRE to do this

SREs’ first job was to hold this ship, but that’s all where they got stuck at

5. What Site Reliability Engineers should’ve built is

SREs should’ve been *engineering* and *observing* the bridge, but instead they became the bridge

Share to:
Twitter
Reddit
Linkedin
#SRE Tooling #sre

You might also like...

We’ve raised a $11M Series A led by Sequoia Capital India!
We’ve raised a $11M Series A led by Sequoia Capital India!

Change is the only constant in a cloud environment. The number of microservices is constantly growing and each of these is being deployed several times a day or week, all hosted on ephemeral servers. A typical customer request depends on at least 3 internal and 1 external service. It’s

Read ->
Why Service Level Objectives?
Why Service Level Objectives?

Understanding how to measure the health of your servcie, benefits of using SLOs, how to set compliances and much more...

Read ->
How to Improve On-Call Experience!
How to Improve On-Call Experience!

Better practices and tools for management of on-call practices

Read ->

SRE with Last9 is incredibly easy. But don’t just take our word for it.