Book Image

Real-World SRE

By : Nat Welch
Book Image

Real-World SRE

By: Nat Welch

Overview of this book

Real-World SRE is the go-to survival guide for the software developer in the middle of catastrophic website failure. Site Reliability Engineering (SRE) has emerged on the frontline as businesses strive to maximize uptime. This book is a step-by-step framework to follow when your website is down and the countdown is on to fix it. Nat Welch has battle-hardened experience in reliability engineering at some of the biggest outage-sensitive companies on the internet. Arm yourself with his tried-and-tested methods for monitoring modern web services, setting up alerts, and evaluating your incident response. Real-World SRE goes beyond just reacting to disaster—uncover the tools and strategies needed to safely test and release software, plan for long-term growth, and foresee future bottlenecks. Real-World SRE gives you the capability to set up your own robust plan of action to see you through a company-wide website crisis. The final chapter of Real-World SRE is dedicated to acing SRE interviews, either in getting a first job or a valued promotion.
Table of Contents (13 chapters)


In this chapter, we talked about what postmortems are, when we should write them, and how to write, discuss and analyze them. We also talked about keeping blame out of postmortems and helping your team to prevent future issues by prioritizing what comes out of the postmortem process.

As an SRE, or as part of an organization that wants reliability, postmortems are the transition from dealing with the present to dealing with the future. Everything above postmortems in the hierarchy is about the future—planning and improving processes. Everything below (monitoring and incident response) is about dealing with the present. Postmortems allow us to look at the past, before we start thinking about the future.

In the next chapter, we will talk about testing and releasing, where we think about code we have written and how we introduce it into the world. We have finished looking at incidents and now will move on to the constant evolution of our products and services.