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

Validating functionality during deployment with automated testing

The joy a developer gets from seeing something work for the first time can be all-consuming. With the feeling of satisfaction often comes a drive to build more, do more, and yes, be even more clever with our code.

Modern systems are becoming more complex than ever, relying on multiple microservices, databases, and even third-party systems. The ability to test every single possibility by hand has become near impossible. With this complexity, it’s not difficult to see why automation has become so highly favored. In an ecosystem where code is developed by individual developers and then merged into a larger code base with multiple inflight development efforts, automated testing ensures that the code, when brought together, still functions as intended.

As testing has progressed from manual point-and-click testing into automation, we also find gaps in many QA engineers understanding of the methodologies of development...