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
- compute options — The main ways to run code in the cloud: virtual machines, containers and functions, each moving a different amount of work to the provider.
- trade-off — A choice that gains one property by giving up another, such as speed bought with staleness.
- system design — The work of deciding how the parts of a software system fit together to meet its requirements, and writing down what each choice costs.
Taught in
- Comparing Compute Options — Cloud Infrastructure & Hyperscaler Architecture
- When to Pick Which Database — Cloud Infrastructure & Hyperscaler Architecture
- What A Design Is For, And How To Run A Design Discussion — Scalable System Design & Distributed Architecture