decision record

A short written note of a technical decision, the facts behind it and the trade-off accepted, so later reviewers understand why.

In more detail

A useful record states the workload’s trigger, duration, state and latency needs, the choice made, and the failure mode it introduces. It keeps technology choices from becoming popularity contests and makes it clear when to revisit them.

Example

context: read heavy, one region. decision: one relational database and a read replica. rejected: a document store. consequence: replica lag is visible after a write.

Related terms

Taught in

References