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

Serverless technology and containers are here to stay. Their place in IT, especially when used in orchestrations, is amazingly powerful, giving us so much capability to provide even more reliability and resiliency in platforms.

Serverless tends to be a less intimidating technology to learn, but at high production levels – say, over a million calls a day – the level of complexity can grow. Even so, for nightly jobs, low volumes, and even compliance and testing, serverless environments can be extremely cost-effective places to do work.

On the other hand, containers and the many ways to orchestrate them are a subject area all their own. There are people who spend their entire careers inside of Kubernetes, running millions of containers in a single orchestration across multiple data centers around the world. You’ll even find specialty divisions dedicated just to running these types of large-scale operations. However, remember, the concepts are the same...