event sourcing
Storing every change to an application's state as an event and rebuilding the current state by replaying those events.
In more detail
It gives a full history of every change, but queries on current state depend on views built from the events. It pairs naturally with an append-only log that keeps every event.
Example
A Kafka topic can serve as the event store.Related terms
- replay — Delivering or returning something again: a stored result for a repeated request, or past events for a client that missed them.
- materialised view — A stored table of results computed from other data, kept so queries do not have to recompute them.
- append-only log — A data structure where new entries are only ever added at the end and existing entries are never changed in place.
Taught in
- Why A Log And Not A Queue — Apache Kafka & Event Streaming