Episode 28 [SREpath Podcast]
Show notes
Sebastian and I got together to react to and discuss 5 passages from Chapter 1 of Google’s Site Reliability Engineering book (2016) by Betsy Beyer, Jennifer Pettof, Niall Murphy, et al.
We covered passages like:
- The sysadmin approach and the accompanying development ops split have a number of disadvantages and pitfalls
- Google has chosen to run our systems with a different approach. Our Site Reliability Engineering teams focus on hiring software engineers to run our products
- The term DevOps emerged in industry. One could equivalently view SRE as a specific implementation of DevOps with some idiosyncratic extensions.
- Google caps operational work for SREs at 50 percent of their time. Their remaining time should be spent using their coding skills on project work.
- Product development and SRE teams can enjoy a productive working relationship by eliminating the structural conflict in their respective goals
Reliability Nut at SREpath
Ash has an unhealthy obsession with software reliability. Maybe it’s got to do with the trauma of working at a few companies where software kept slowing or went down while he worked to turn it around. His ma hopes that he can one day turn this passion into a respectable job or business. Still waiting…
Latest posts by Ash Patel (see all)
- #34 From Cloud to Concrete: Should You Return to On-Prem? – March 26, 2024
- #33 Inside Google’s Data Center Design – March 19, 2024
- #32 Clarifying Platform Engineering’s Role (with Ajay Chankramath) – March 14, 2024