Chapter 56. What Is Toil, and Why Are SREs Obsessed with It?
Zachary Nickens
Site reliability engineers love to hate toil, but what is toil? Why are SREs obsessed with removing toil? Site reliability engineering is what happens when you treat operations like a software problem. How do you treat ops like a software problem?
SRE can feel opaque, but in practice, it is the essence of engineering: remove inefficiencies in one component so that other components may perform quantifiably better. Software engineers want their code to be simple, fast, and reliable: bug and cruft free. SREs want operations to be bug and cruft free! Cruft and bugs in ops and infrastructure can be described in one word: toil. Toil is the kind of work tied to running a production service that tends to be manual, repetitive, automatable, tactical, and devoid of enduring value, and that scales linearly as a service grows. Toil is any engineering effort devoid of meaningful value.
If a piece of software is going to be used, we should make commitments, at a minimum to ourselves, that it is reliable, secure, and observable—but there is no such thing as 100% reliable or 100% secure. When an issue occurs, software engineers need to be able to identify the issue, remediate or recover, and restore service. Slowing down to find all potential problems before release isn’t the answer. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access