Reliability Enablers (SREpath)
Reliability Enablers
#29 - Reacting to Google's SRE book 2016 (Chapter 1 Part 2)
0:00
-31:25

#29 - Reacting to Google's SRE book 2016 (Chapter 1 Part 2)

Sebastian and I continue our breakdown of notable passages from Chapter 1 of Google's Site Reliability Engineering (2016) book by Betsy Beyer, Jennifer Pettof, Niall Murphy, et al.

We covered passages like:

  1. Monitoring is one of the primary means by which service owners keep track of a system's health and availability.

  2. Efficient use of resources is important anytime a service cares about money.

  3. Humans add latency, even if a given system experiences more actual failures. A system that can avoid emergencies that require human intervention will have higher availability than a system that requires hands on intervention.

  4. SRE has found that roughly, 70 percent of outages are due to changes in a live system. Best practices in this domain use automation to accomplish implementing progressive rollouts.

  5. Demand forecasting and capacity planning can be viewed as ensuring that there is sufficient capacity and redundancy to serve projected future demand, the required availability.

0 Comments
Reliability Enablers (SREpath)
Reliability Enablers
Software reliability is a tough topic for engineers in many organizations. The Reliability Enablers (Ash Patel and Sebastian Vietz) know this from experience. Join us as we demystify reliability jargon like SRE, DevOps, and more. We interview experts and share practical insights. Our mission is to help you boost your success in reliability-enabling areas like observability, incident response, release engineering, and more.