Event sourcing: keep every change, not just the latest state
Most software stores the current state of things: this account holds $40. An event-sourced system stores what happened instead: deposited $100, withdrew $60. The balance is worked out by replaying the events.
The idea, in one ledger
Accountants worked this way long before computers. A ledger is never edited; a mistake is fixed with a new correcting entry, so the history of every change survives. Martin Fowler described the software version as Event Sourcing in 2005, and Greg Young popularised it alongside CQRS from about 2010.
Every change becomes an event, written once to an append-only log and never altered. The current state is a projection: read the events in order, apply each one, and you arrive at today.
What you get for it
- A full audit trail. You can say exactly what changed, when, and in what order, because that record is the database.
- Time travel. Replay the log up to any moment and you see the system as it stood then. Bugs that depend on history become reproducible.
- New views of old data. Need a report nobody planned for? Write a new projection and run every past event through it.
What it costs
Events are permanent, so their shape is too. Change what an event means and you must keep reading every old version of it forever, or write upcasters to translate them. This is the part teams underestimate.
Reads are eventually consistent: the projection lags the log by a moment, and the interface has to allow for it. Deleting personal data is awkward in a log built never to forget; the usual answer is to encrypt each person's data with their own key and throw the key away.
The honest rule: use it where history is the product, such as money, orders, inventory and anything audited. A blog does not need it.
What you could build here
Three directions that would work on this name. None of them is the only answer — it is your name once it is yours.
- A field guide to event sourcing. Patterns, worked examples and the failure stories nobody writes up. Developers search this topic when a system is already in trouble; a site that answers them straight earns their trust for good.
- A hosted event store. Append-only storage with projections and replay built in, sold to teams who want the pattern without running the database themselves.
- A consultancy front door. Event-sourced systems are hard to get right and expensive to get wrong. A name that says exactly what you do is worth more than any ad spend.
Read further
- Martin Fowler: Event SourcingThe 2005 write-up that named the pattern
- Microsoft: Event Sourcing patternWhen to use it, and the issues to plan for
- Text Diff OnlineFree side-by-side text comparison
This domain is for sale
- 2026-10-07registered
- Newage
- COMextension
- Cleannever spammed
A memorable, brandable name for a well-known software pattern. Suits a developer publication, an event-store product, or a consultancy that specialises in it.