Skip to content

Files

Latest commit

dea2316 · Jan 1, 2018

History

History
This branch is 2178 commits behind iluwatar/java-design-patterns:master.

event-sourcing

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Nov 28, 2017
Dec 31, 2017
Aug 12, 2017
Jan 1, 2018
layout title folder permalink categories tags
pattern
Event Sourcing
event-sourcing
/patterns/event-sourcing/
Architectural
Java
Difficulty Intermediate
Performance

Intent

Instead of storing just the current state of the data in a domain, use an append-only store to record the full series of actions taken on that data. The store acts as the system of record and can be used to materialize the domain objects. This can simplify tasks in complex domains, by avoiding the need to synchronize the data model and the business domain, while improving performance, scalability, and responsiveness. It can also provide consistency for transactional data, and maintain full audit trails and history that can enable compensating actions.

alt text

Applicability

Use the Event Sourcing pattern when

  • You need very high performance on persisting your application state even your application state have a complex relational data structure
  • You need log of changes of your application state and ability to restore a state of any moment in time.
  • You need to debug production problems by replaying the past events.

Real world examples

Credits