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...

How we won Dukaan over
How we won Dukaan over

5 meetings. 1 month. From introductions, to a demo, and ultimately winning Dukaan over. Subhash and his team’s velocity on decision-making, moving fast, and radical candor, is a breath of fresh air in the Indian startup ecosystem.

Read ->
Sample vs Metrics vs Cardinality
Sample vs Metrics vs Cardinality

When dealing with Time Series databases, I always got confused with Sample vs Metrics vs Cardinality. Here’s an explanation as I have understood it.

Read ->
How to calculate HTTP content-length metrics on cli
How to calculate HTTP content-length metrics on cli

A simple guide to crunch numbers for understanding overall HTTP content length metrics.

Read ->

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