
What an incident is in plain words: how to tell an outage from a bug, Google's three questions for declaring one, and why the incident commander fixes nothing.

What a runbook is and how it differs from documentation: when to write one, the five blocks inside it, and the rule that commands get copied, not described.

What a postmortem is in plain words: why you write outages down, why there are no names in it, and the one mistake that makes the whole document useless.

What graceful shutdown means in plain words: how an app should die, why the signal often never arrives in Docker, and what the 30 seconds of grace are for.

How to build a status page for your project: where to host it, what should check availability, and why status on your own domain is a bad idea. Five steps.

What a circuit breaker is, in plain words: a fuse that stops calling a service that's already down. The three states, and how it differs from a rate limit.

A fallback is your backup plan when the main path fails. How it differs from a retry, how to build a ladder of backups, and why a silent fallback is dangerous.

A health check is a simple URL that answers «I'm running». Step by step: two separate endpoints, timeouts, and the mistake that takes your whole service down.