liveBook · Manning

Event sourcing

Event sourcing is a persistence pattern in which state changes are recorded as an ordered sequence of events from which application state can be derived.

How 2 Manning books explain it

Kafka for Architects

An event-sourced system persists state changes as an ordered sequence of events from which current state can be reconstructed.

How it is used
Uses Kafka’s retained event log as the authoritative history for reconstructing state and supporting event-driven processing.
How deep it goes
Explains immutable events, replay, retention, snapshots, and database trade-offs, but stops short of implementation walkthroughs.
Examples
Demonstrates customer-address replay and order enrichment through a change-log join.
What you can do after
Evaluate Kafka event-sourcing designs by balancing replayability, snapshots, query needs, retention cost, and database fit.

Read how Kafka for Architects explains event sourcing →

Akka in Action, Second Edition

Event sourcing is a persistence technique that stores state changes as an ordered sequence of events and reconstructs current state by replaying them.

How it is used
Uses a journal to make actor state durable and recoverable while keeping application logic expressed through messages.
How deep it goes
Explains commands, validation, event append, replay, immutability, and versioned deserialization; defers event-adapter details.
Examples
Uses Conversation actors with MessageAdded events and cargo events whose schemas gain or lose fields over time.
What you can do after
Operate persistent actors by validating commands, appending events, replaying journals, and accommodating event-schema versions.

Read how Akka in Action, Second Edition explains event sourcing →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.