Part 1 of 6 · 1 min read
Why this page comes fifth
In this module you will
- Describe what happens from the moment an alert fires until the incident is closed.
- Explain why mitigation comes before finding the root cause.
- Name the usual roles in an incident and what each does (common practice, not from the books).
- Say when a postmortem is needed and what it must contain.
- Explain why blameless learning and practice drills make systems safer.
Modules 1 to 4 reduce the chance and the cost of failure. They cannot reduce either to zero. This page covers what people do when something breaks anyway. The books say less here than elsewhere, so the sources are short: "Understanding Distributed Systems" (UDS) chapter 20 on on-call and postmortems, "Building Microservices" (BM) chapter 11 on blameless culture and failure drills, and one real case in "Designing Data-Intensive Applications" (DDIA). The role names and the timeline layout are common practice, not from the books. Numbers marked "made up" only show the idea.