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

The subject of GitOps can fill entire books. As rockstar SREs, we learned to leverage pipeline automation to meet our goals. We can reduce toil by automating not only deployments but also security and compliance scanning, testing, opening change requests, and providing developers with feedback, enabling them to iterate faster.

The true value of the pipeline is testing. We talk about making SRE proactive instead of reactive all the time, looking for ways in which we can prevent downtime – instead of responding to an issue at 2 a.m. – working to end the expense of half a dozen or more people on an outage call, which steals time away from development. Testing is the one proactive tool that absolutely works.

In addition, we walked through a GitHub Actions pipeline to illustrate just how simple it is to add additional steps and hopefully brought you some real understanding of pipelines.

Next up, we’ll discuss serverless deployment, containers, and Kubernetes...