System of record (source of truth)
The one system whose copy of a piece of data wins when copies disagree; all other copies are derived from it.
Every important piece of data, such as bookings, customer records or prices, should have exactly one system of record. Search indexes, caches, reports and other services hold copies that are rebuilt from it. When there are two masters, every disagreement becomes a meeting.
In a migration the system of record moves, and that move is the riskiest step. A common sequence: the legacy system stays the source of truth while the new one is fed by change data capture; a parallel run compares results; then the direction flips and the legacy system becomes a read-only copy until it is switched off. Writing to both as equals is the dual-write problem. In the strangler fig pattern this is decided per domain, not for the whole system at once.
Related terms
- Dual-write problem: Writing one change to two systems, such as a database and a broker or an old and a new store, without a shared transaction, so they can drift apart.
- Strangler fig pattern: Replacing a legacy system piece by piece, routing one feature at a time to new code until the old system can be switched off.
- CDC (change data capture): Reading committed changes from a database’s own transaction log and streaming them as events to other systems.
- Parallel run (shadow traffic): Running the old and new implementation side by side on real requests, using the old result and comparing the new one, before switching over.
