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

The cost of more reliability as a business decision

I wish every outage came with a six-figure remediation budget to shore up our code, systems, and architecture – trust me, you’d be hard-pressed to see this once in your career as a rockstar SRE.

The truth is that reliability costs – and cost often comes down to being a business decision. With that in mind, we’ll not only discuss the technical side of these reliability options but also, more importantly, the cost of both outage time and budget.

Active:Active

A very basic and highly effective strategy is to create two copies of an architecture and put them in different data centers or regions. You use some type of load balancing that distributes load between the two. The downside is that for zero-impact outage deployments, you still require retries in your applications. Also, you have to have enough capacity online, often called spinning capacity, to accept the entire load in both data centers and...