Book Image

Becoming a Rockstar SRE

By : Jeremy Proffitt, Rod Anami
Book Image

Becoming a Rockstar SRE

By: Jeremy Proffitt, Rod Anami

Overview of this book

Site reliability engineering is all about continuous improvement, finding the balance between business and product demands while working within technological limitations to drive higher revenue. But quantifying and understanding reliability, handling resources, and meeting developer requirements can sometimes be overwhelming. With a focus on reliability from an infrastructure and coding perspective, Becoming a Rockstar SRE brings forth the site reliability engineer (SRE) persona using real-world examples. This book will acquaint you the role of an SRE, followed by the why and how of site reliability engineering. It walks you through the jobs of an SRE, from the automation of CI/CD pipelines and reducing toil to reliability best practices. You’ll learn what creates bad code and how to circumvent it with reliable design and patterns. The book also guides you through interacting and negotiating with businesses and vendors on various technical matters and exploring observability, outages, and why and how to craft an excellent runbook. Finally, you’ll learn how to elevate your site reliability engineering career, including certifications and interview tips and questions. By the end of this book, you’ll be able to identify and measure reliability, reduce downtime, troubleshoot outages, and enhance productivity to become a true rockstar SRE!
Table of Contents (27 chapters)
1
Part 1 - Understanding the Basics of Who, What, and Why
5
Part 2 - Implementing Observability for Site Reliability Engineering
10
Part 3 - Applying Architecture for Reliability
16
Part 4 - Mastering the Outage Moments
20
Part 5 - Looking into Future Trends and Preparing for SRE Interviews

Summary

In this chapter, we explored the importance of an SLA and its creation, which, as we remember, is more about the relationship between business and technology. Even though we don’t always have a say in our SLAs (especially for TOS, base offerings, or existing MSAs), conversations with your vendors focusing on what is best for both companies to be profitable often lead to more trust and even provide paths that not all customers may have to resolve issues. We also explored how not all SLAs require immediate action or 100% uptime, and how potential impact should be the driving force in the response.

As we dove into the SLI, the measure of health, we reviewed not only how finding the right way to measure is important but also how outside influences can impact getting a correct measurement. We also took a look at SLOs, often used as a tipping point for working versus broken, and how their view with respect to time is so important.

And remember, an SLI is as simple as...