Book Image

Real-World SRE

By : Pavlos Ratis, Nat Welch
Book Image

Real-World SRE

By: Pavlos Ratis, Nat Welch

Overview of this book

Real-World SRE is the go-to survival guide for the software developer in the middle of catastrophic website failure. Site Reliability Engineering (SRE) has emerged on the frontline as businesses strive to maximize uptime. This book is a step-by-step framework to follow when your website is down and the countdown is on to fix it. Nat Welch has battle-hardened experience in reliability engineering at some of the biggest outage-sensitive companies on the internet. Arm yourself with his tried-and-tested methods for monitoring modern web services, setting up alerts, and evaluating your incident response. Real-World SRE goes beyond just reacting to disaster—uncover the tools and strategies needed to safely test and release software, plan for long-term growth, and foresee future bottlenecks. Real-World SRE gives you the capability to set up your own robust plan of action to see you through a company-wide website crisis. The final chapter of Real-World SRE is dedicated to acing SRE interviews, either in getting a first job or a valued promotion.
Table of Contents (16 chapters)
Real-World SRE
Contributors
Preface
Other Books You May Enjoy
Index

Experience of tools


There are lots of things you can do to improve your tools. Often, they are found just by treating your tools like products. This means not treating them like throwaway scripts and not just hacking on them as needed. Instead, they need to be invested in, loved, and maintained.

One way this often comes out is by having what is referred to as opinionated tools. This means tools that do not support every single possible workflow. Instead, they focus on the right and wrong way to do things. The downside of this is that tools can be unable to support new workflows when they grow within the organization. As an upside, though, you as the maintainer know exactly what workflows exist and how they work, and can research improving them to make the experience better.

That does not mean that tools should not be configurable. I, personally, love configuring tools through configuration files and environment variables. Configuration files are great when you need to keep all of your configuration...