Please enable JavaScript.
Coggle requires JavaScript to display documents.
Event Sourcing and Event-Driven Architecture — In Under 5 Minutes! -…
Event Sourcing and Event-Driven Architecture — In Under 5 Minutes!
Events are the building blogs of all the web applications
Event-Driven
General architectural pattern that uses events to trigger actions
When to use?
More than one person needs to read from the same dataset
All changes must be stored in an append-only fashion
To be analyzed later on
To be audited
Suitable for systems that have high throughput and latency requirements
Easier to scale
Event Sourcing
General properties
Data is stored as a series of events, capturing a snapshot of the application's conditions
Event identifier is unique among all other events
Event properties represent what has happened since the last one was added
Is a pattern for persisting the history of changes to an application's state
Can be used to replay past states of your application
A technique to implement Event-Driven architecture
Advantages
Transactions are immutable and recorded as a sequence of events
Events can be replayed at any time if needed, even years later
Good for systems that need to maintain historical data and audit trails