RTE logo
← Back to architecture map
Architecture Pattern

Event Sourcing

Don't store current state; store every event that ever happened and replay to rebuild state.

state

Flow From Map

1. AccountOpened(100)
2. Deposited(50)
3. Withdrew(30)
replay → balance = 120

Your POC Area

Replace this placeholder with your interactive proof of concept for Event Sourcing. This route is already dedicated to this pattern, so you can add diagrams, controls, code demos, or simulations here.

Example references: EventStore, Axon, eventstore-db-client

Comments

Sign in to leave a comment. Your name and photo come from Google; nothing else is shared.

Loading comments...