An event reports that something occurred; handlers update state and may emit new commands or events. Idempotency and ordering rules prevent duplicate or late events from corrupting progress.

Event-Driven Graphs React to Facts

Durable execution records enough state and event history to resume after crashes without losing progress or duplicating effects. Persistence boundaries belong in graph semantics, not only infrastructure.

Durable Execution Survives Process Failure

Event sourcing stores an append-only sequence of domain events and derives current state by replay. It improves auditability but requires event versioning, snapshots, and privacy-aware correction strategies.

Event Sourcing Rebuilds State From Accepted Events

An idempotent operation can be retried with the same key without multiplying its intended effect. It is essential when acknowledgements can be lost after an action succeeds.

Learn Before

Related