Best books for Site Reliability Engineers (SREs)

Site Reliability Engineering: How Google Runs Production Systems

by Betsy Beyer, Chris Jones, Jennifer Petoff, Niall Richard Murphy · 2016

~520 pages~13 hrs to read

The founding text on SLOs, error budgets, toil, monitoring and incident response. Read it in your first months to learn the vocabulary the rest of the field uses; skim chapters outside your stack.

Incident Management for Operations

by Rob Schnepp, Ron Vidal, Chris Hawley · 2017

~160 pages~4 hrs to read

Adapts the incident command model from emergency services to IT operations: roles, communication, handoffs. Useful before your first on-call rotation and when you start running incidents.

Practical Monitoring: Effective Strategies for the Real World

by Mike Julian · 2017

~170 pages~4 hrs to read

Covers monitoring strategy, alert design, on-call practice and tool choice without vendor focus. A good first read when you inherit noisy alerts or need to build monitoring for a service from scratch.

The Site Reliability Workbook: Practical Ways to Implement SRE

by Niall Richard Murphy, Betsy Beyer, David K. Rensin, Kent Kawahara, Stephen Thorne · 2018

~500 pages~13 hrs to read

Companion to the first book with worked examples: SLO engineering, alerting on SLOs, canarying, on-call and incident response. Pick it up when you are writing real SLOs and alerts for your own services.

Implementing Service Level Objectives

by Alex Hidalgo · 2020

~350 pages~9 hrs to read

A full treatment of choosing SLIs, setting targets, computing error budgets and using them in planning. Read it when you need to turn SLOs from a slide into decisions your team makes.

Observability Engineering

by Charity Majors, Liz Fong-Jones, George Miranda · 2022

~400 pages~10 hrs to read

Explains debugging production through high-cardinality events, tracing, sampling and SLO-based alerting. For SREs moving beyond dashboards and threshold alerts to questions they did not predict.

Designing Data-Intensive Applications

by Martin Kleppmann · 2017

~620 pages~16 hrs to read

Replication, partitioning, transactions, consistency and consensus explained for people who run these systems. It gives you the model to reason about why databases and queues fail the way they do.

Release It!: Design and Deploy Production-Ready Software

by Michael T. Nygard · 2007

~380 pages~10 hrs to read

Stability patterns and anti-patterns such as timeouts, circuit breakers and bulkheads, drawn from production failures. Read it to review service designs and to explain outages by cause.

Systems Performance

by Brendan Gregg · 2013

~930 pages~23 hrs to read

A methodical guide to analysing CPU, memory, disk and network behaviour on Linux, including the USE method and tracing tools. Use it for capacity work and for performance incidents the dashboards cannot explain.

Chaos Engineering: System Resiliency in Practice

by Casey Rosenthal, Nora Jones · 2020

~400 pages~10 hrs to read

Practitioner accounts of designing and running failure experiments, from hypotheses to organisational buy-in. For senior SREs introducing resilience testing and game days to a team.

Platform Engineering: A Guide for Technical, Product, and People Leaders

by Camille Fournier, Ian Nowland · 2024

~330 pages~8 hrs to read

Covers building and staffing an internal platform team, treating the platform as a product, and measuring its value. For SREs moving into platform work or leading a team that supports other engineers.

Team Topologies: Organizing Business and Technology Teams for Fast Flow

by Matthew Skelton, Manuel Pais · 2019

~240 pages~6 hrs to read

Describes stream-aligned, platform, enabling and complicated-subsystem teams and how they interact. Helps senior SREs decide how reliability and platform teams should work with product teams.