Event Sourcing.¶
Fowler, M. (2005). Event Sourcing. martinfowler.com.
Cited by¶
5 citations across 5 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Event-Centered Modeling
- In software it is event sourcing, where application state is not stored directly but computed by replaying an append-only log of events — the same wiring as the historiographic case on a different substrate.
This sourceDefines event sourcing — application state computed by replaying an append-only log of immutable events, with snapshots and projections — the software instance of event-centered modeling.
- In software it is event sourcing, where application state is not stored directly but computed by replaying an append-only log of events — the same wiring as the historiographic case on a different substrate.
- Immutability
- The concept crystallized in computer science—where the immutable object, the persistent data structure, and the append-only log are now standard building blocks—but the same write-once discipline governs executed legal instruments, the unalterable accounting journal, content-addressed version-control commits, and append-only distributed ledgers.
This sourceArticulates the append-only event log as the authoritative record across software systems, treating apparent change as appended events and current state as a derivation by replay—the same write-once discipline that recurs in ledgers and audit trails.
- The concept crystallized in computer science—where the immutable object, the persistent data structure, and the append-only log are now standard building blocks—but the same write-once discipline governs executed legal instruments, the unalterable accounting journal, content-addressed version-control commits, and append-only distributed ledgers.
- Logging
- The pattern supports the log-determinism inference: if a system's behaviour is a function only of the log plus deterministic processing, then replaying the log reproduces the behaviour
This sourceDescribes recording all state changes as an ordered append-only event log so that replaying the log deterministically reconstructs current state.
- The pattern supports the log-determinism inference: if a system's behaviour is a function only of the log plus deterministic processing, then replaying the log reproduces the behaviour
- Identity-Preserving Modification
- This composition logic underwrites event-sourced architectures in software, amendment chains in law, and history reconstruction in medicine and cultural heritage, all of which solve the same problem — how to know the current state's warrant — by following the chain back to the originating event.
This sourceArchitectural pattern of storing the full ordered sequence of state-changing events against an identifier and reconstructing current state by replaying them.
- This composition logic underwrites event-sourced architectures in software, amendment chains in law, and history reconstruction in medicine and cultural heritage, all of which solve the same problem — how to know the current state's warrant — by following the chain back to the originating event.
Mechanisms¶
- Ratchet Event Log
- It is the disciplined-provenance idea behind an event-sourced system, where current state is derivable from the ordered log of events.
This sourceDefines event sourcing as storing every state change in an ordered event sequence from which application state can be rebuilt.
- It is the disciplined-provenance idea behind an event-sourced system, where current state is derivable from the ordered log of events.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:1e52141ddcae · see in the full table