November 2020
Beginner to intermediate
250 pages
7h 41m
English
Content preview from 97 Things Every SRE Should Know
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 84. Trading Places: SRE and Product
Shubheksha Jalan
Historically, there’s been a tension between SRE teams and product and feature teams akin to the wall between ops and dev teams. The former want to optimize for reliability first and foremost, whereas the latter want to ship, which leads to change—which leads to things breaking. We don’t need to live with this oppositional relationship. If we can build empathy between product and SRE teams, it will not only lead to a healthier relationship, it will be a stronger win–win outcome for everyone.
How does this happen? It’s important for engineers on both teams to be in each other’s shoes to understand and make the right trade-offs. When product engineers don’t operate with a reliability mindset, they shift an unfair burden onto SREs that can lead to unpleasantness and, in the worst case, burnout. When SREs don’t adopt a product-engineer perspective, they might not understand the pressure from executives and stakeholders, and both teams miss the opportunity to broaden their knowledge.
The ideal scenario here would be for each feature team to be responsible for running its own service rather than for the SREs to be paged in the middle of the night. However, this isn’t always possible. On call is hard. It can be disruptive and taxing even when done well. If it lacks empathy or care, it can have disastrous consequences. Engineers ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.