Book
Site Reliability Engineering
How Google Runs Production Systems
Betsy Beyer, Chris Jones, Jennifer Petoff, Niall Richard Murphy
Summary
Compiled by four Google engineers from the practices Google's Site Reliability Engineering team developed over roughly a decade, this book introduced the vocabulary, SLI, SLO, error budget, toil, that much of the industry now uses to talk about production reliability. Its central move is the error budget: instead of treating "zero outages" as the goal, a service's SLO defines how much unreliability is acceptable in a period, and that budget is spent deliberately on the risk of shipping new features, turning a political argument between developers and operators into an engineering tradeoff. The book covers this alongside monitoring, on-call practice, incident management, postmortem culture, and load balancing at Google's scale, treating reliability engineering as software engineering applied to operations, not a separate discipline.
Target Readers
- Operations teams stuck negotiating feature velocity against uptime who want the error-budget framework that resolves that conflict
- Engineers designing SLIs and SLOs for a service who need the reasoning Google's SRE team built them on, not just the formulas
- Organizations standing up an SRE function who want the source text before adapting practices to their own scale
Tags
Colophon
- Publisher
- O'Reilly Japan
- ISBN
- 978-4873117911
- Published
- Aug 2017
- List price
- ¥5,280incl. taxMay differ from the actual selling price on Amazon
Get this book
* The link above is an advertisement via Amazon Associates.Related Books
Prerequisites
- Recommended
The DevOps Handbook
How to Create World-Class Agility, Reliability, and Security in Technology Organizations
Gene Kim, Jez Humble, Patrick Debois, John Willis
Reason: Where 'The DevOps Handbook' preaches collaboration between development and operations, Google's 'Site Reliability Engineering' shows the concrete form of solving the operations side 'with software engineering'. With error budgets and SLOs to engineer reliability, it is a natural evolution of DevOps.
- Related
Practical Monitoring
Effective Strategies for the Real World
Mike Julian
Reason: After designing 'what to measure' with 'Practical Monitoring', advance to the philosophy of tying those metrics to organizational decisions. Google's 'Site Reliability Engineering' elevates monitoring data—via SLIs/SLOs/error budgets—into criteria for 'when to halt feature work and invest in reliability'.
- Related
Release It!, 2nd Edition
Design and Deploy Production-Ready Software
Michael T. Nygard
Reason: The stability patterns in 'Release It!' make individual services harder to break, but how to set targets for whole-system reliability and operate it organizationally is a separate question. Google's 'Site Reliability Engineering' integrates individual fault-tolerant design into organizational reliability management through error budgets and incident-response structures.
- Related
Team Topologies
Organizing Business and Technology Teams for Fast Flow
Matthew Skelton, Manuel Pais
Reason: After designing an organization for fast flow of value with 'Team Topologies', you arrive at the question of which team owns reliability and how. Google's 'Site Reliability Engineering' presents concrete practices—error budgets, sharing of operational responsibility—for embedding reliability as organizational culture.
Next Books
- Prerequisite
The Site Reliability Workbook
Practical Ways to Implement SRE
Betsy Beyer, Niall Richard Murphy, David K. Rensin, Kent Kawahara, Stephen Thorne
Reason: Where 'Site Reliability Engineering' articulates principles distilled from Google's practice, its sequel 'The Site Reliability Workbook' shows 'how to implement it at your own company' with concrete procedures and case studies. Theory first, then the implementation volume—a required progression.
- Recommended
Observability Engineering
Achieving Production Excellence
Charity Majors, Liz Fong-Jones, George Miranda
Reason: SRE presupposes 'knowing the exact state of the system' to meet SLOs, but the SRE book itself stays at the philosophy of monitoring. 'Observability Engineering' supplements the techniques—distributed tracing, high-cardinality events—to explore unknown failures, satisfying at the implementation level the observation capability SRE demands.
- Recommended
Building Secure and Reliable Systems
Best Practices for Designing, Implementing, and Maintaining Systems
Heather Adkins, Betsy Beyer, Paul Blankinship, Piotr Lewandowski, Ana Oprea, Adam Stubblefield
Reason: Once SRE lets you handle reliability as engineering, you arrive at the question 'aren't security and reliability fundamentally the same design problem?'. Google's 'Building Secure and Reliable Systems' extends SRE to show principles for building security into system design rather than bolting it on, integrating reliability and security.
- Related
Seeking SRE
Conversations About Running Production Systems at Scale
David N. Blank-Edelman
Reason: After learning Google-originated SRE theory, you want to know how others adapt and practice it. Edited by Blank-Edelman, 'Seeking SRE' is a collection of contributions from many practitioners, offering diverse applications of SRE in non-Google contexts and broadening the scope of the principles.
Sources
- Related
LLMOps
Managing Large Language Models in Production
Abi Aryan
Reason: Where Google's 'Site Reliability Engineering' frames engineering reliability for general services via SLIs/SLOs and error budgets, 'LLMOps' applies that operating philosophy to the new target of LLM applications, organizing the production concerns—including governance and cost management—specific to running them.