source of truth
The one authoritative place a fact is recorded, from which every copy is derived instead of being maintained separately.
In more detail
When two copies disagree, the source of truth wins and the copy is regenerated or repaired from it. Every other copy, such as a cache, a report or generated documentation, should be rebuildable from it. Document where it lives, and compare copies against it to find and repair drift.
Example
In a denormalised database design, the original table stays the source of truth for every copied column.Related terms
- OpenAPI — A standard, language-neutral format for describing an HTTP API: its paths, operations, parameters, request and response schemas, errors and security.
- API contract — The written promise an API makes about its operations, inputs, outputs and errors, which callers rely on while the code behind it changes.
- GitOps — Operating a system by keeping its desired state in Git and letting a controller continuously make the live system match it.
- desired state — A description of how a machine should look when the work is finished, rather than a list of steps to get there.
- denormalisation — Deliberately storing a copy of data in a second place, usually to make reads faster by avoiding a join.
- normalisation — Designing tables so each fact is stored in exactly one place, by splitting repeated data into related tables.
- projection — A copy of data reshaped for one purpose, such as a search index or cache, built from the source of truth.
- reconciliation — Comparing copies of data with the source of truth and correcting any that have drifted.
- data ownership — The rule that each piece of data has exactly one service or team that writes it and defines what it means.
Taught in
- What An API Is, And The Alternatives — Modern API Architecture: REST, GraphQL & gRPC
- OpenAPI And Design-First — Modern API Architecture: REST, GraphQL & gRPC
- Contract Testing — Modern API Architecture: REST, GraphQL & gRPC
- What is GitOps? — Continuous Integration & Continuous Delivery Pipelines
- Image Update Automation — Continuous Integration & Continuous Delivery Pipelines
- When To Denormalise On Purpose — PostgreSQL, Indexing & Relational Data Modeling
- The Storage Decision: Relational Versus Document — Scalable System Design & Distributed Architecture
- The Storage Decision: Key Value, Search And Blob — Scalable System Design & Distributed Architecture
- Eventual Consistency And What It Costs A Product — Scalable System Design & Distributed Architecture
- Worked Design Three: A Metrics Ingestion Pipeline — Scalable System Design & Distributed Architecture