Site Reliability Engineering: How Google Runs Production Systems

The book that gave an entire discipline its vocabulary. Written by the Google engineers who invented the role, Site Reliability Engineering explains how a company runs enormous systems by treating operations as a software problem — and it is the origin of terms like error budget and SLO that every infrastructure team now uses.

What the book covers

• The SRE model: what the role is, and the 50% cap on operational work
• Service level indicators, objectives and agreements — and how to choose numbers that mean something
• Error budgets, and how they resolve the fight between velocity and stability
• Eliminating toil, and automation as a first-class engineering output
• Monitoring, alerting philosophy, and avoiding pages nobody should receive
• Release engineering, canarying, and simplicity as a reliability strategy
• Incident response, on-call practice, and blameless postmortem culture
• Distributed consensus, load balancing, cascading failures and overload handling

Who it’s for

SREs, platform and DevOps engineers, and engineering managers designing on-call and reliability practice. Written as a collection of essays, so it reads well out of order.

Edition details

• Authors: Betsy Beyer, Chris Jones, Jennifer Petoff, Niall Richard Murphy
• Publisher: O’Reilly Media
• Format: Paperback
• ISBN: 978-1491929124
• Language: English

Ships free within the United States from Shelfcove.