Site Reliability Engineering, 2nd Edition
by Betsy Beyer, Chris Jones, Christof Leng, David Huska, Jennifer Petoff, Niall Richard Murphy
Chapter 1. Introduction: Modeling What We Do and Why
No matter how feature-rich a software product is, it is ultimately useless to the user if it is down, unusably slow, or inaccurate. To solve this fundamental problem and ensure businesses can reliably deliver their services, Site Reliability Engineering (SRE) has evolved into a broad industry movement. But what exactly is SRE?
Note
The term SRE can be used to describe the field as a whole (Site Reliability Engineering), the individual doing the job (Site Reliability Engineer), and the team that individual is part of (the SRE team). Please keep this context in mind as you read the book. While most of the time in this chapter SRE refers to the field, there are cases where we are talking about individuals and teams.
At first glance, the name may seem a bit odd, but each word has a deeper meaning—and together, they give a pretty good high-level description of what SRE is about:
- Site: The why
-
The first word in the name may be the most confusing one. It is much easier to understand when you know the origins of SRE. When the SRE function was established at Google in 2003, its mission was straightforward: “Keep the site (google.com) up.” Today, of course, the role of SRE teams across the industry is much more nuanced. But the core value remains: a direct connection to business impact. Enabling users to use the company’s products and services is why SRE exists. The dedication to the user is at ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access