(2) Event Sourcing Pattern - Distributed Design Patterns | LinkedIn thumbnail
(2) Event Sourcing Pattern - Distributed Design Patterns | LinkedIn
www.linkedin.com
When we want to retrieve the current state of the data, we simply “replay” all of the events in the event store, starting from the beginning Event Sourcing is based on the idea that every change to the data should be recorded as an event. Event Sourcing is a pattern that suggests storing the history
1 Users
0 Comments
19 Highlights
0 Notes

Top Highlights

  • When we want to retrieve the current state of the data, we simply “replay” all of the events in the event store, starting from the beginning
  • Event Sourcing is based on the idea that every change to the data should be recorded as an event.
  • Event Sourcing is a pattern that suggests storing the history of all changes made to an application’s data as a sequence of events. Rather than storing the current state of the data, Event Sourcing stores the sequence of events that led to that state. In other words, instead of storing the result of each operation, we store the operation itself.
  • When an operation is performed on the data, instead of updating the current state of the data in the database, an event is created that describes the operation
  • Audit Trail: Since all changes to the data are stored as events, we have a complete audit trail of what happened in the application, and when.

Tags

Event Sourcing

Ready to highlight and find good content?

Glasp is a social web highlighter that people can highlight and organize quotes and thoughts from the web, and access other like-minded people’s learning.