Glossary
Every term the courses use, defined in one line and then in a paragraph. Written to be read out of order.
Showing 4 of 4 matching “Incident”
The agreed shape of messages between systems.
What each side promises the other about requests and responses. Exists whether or not anyone wrote it down. Shared types turn a broken contract into a build error instead of a production incident.
See also API, Breaking change
Something is broken for real users right now.
Stop the impact first, understand it second. "What changed recently" answers most incidents, and rolling back is the cheapest action available.
See also Rollback, Postmortem
A written account of an incident, without blame.
What happened, what the impact was, and what allowed it to reach users. The useful question is never who did it but which missing check would have caught it.
Putting the previous version back.
The cheapest available response to a bad deploy and the correct first move in most incidents. Restores your code, not your data: deleted rows and sent emails do not come back.