Events sourcing is the process of processing events that reflect changes maid to a system after the fact. The concept is fairly simple but it's implementation can be quite complex.
A very goo description - https://dev.to/barryosull/event-sourcing-what-it-is-and-why-its-awesome
Events sourcing has many benefits of being implemented using CQRS
Events can be called state transitions but preferable they are called events. Never have getters and setters.
Event Sourcing: Without Eventual Consistency?
- Articles
- Books
- CQRS
- Commands
- Events
- Links
- Notes
- Optimistic-concurrency-control
- Set-validation
- Videos
- event-version
- INTERESTING-STUFF
"From Greg Young"
Let's say every message has 3 ids. 1 is its id. Another is correlation, the last is causation. If you are responding to a message, you copy its correlation id as your correlation id, its message id is your causation id. This allows you to see an entire conversation (correlation id) or to see what causes what (causation id).
- Functional Programming with DDD
- [West LA Go Meetup] Jamie Isaacs - Event Modeling: From Sticky Notes to Go
- GregYoung 8 CQRS Class
CQRS and Event Sourcing Introduction with Greg Young
https://dev.to/barryosull/event-sourcing-what-it-is-and-why-its-awesome
CQRS: cqrs.md) [Commands]: commands.md [Events]: events.md [Links]: links.md [Notes]: notes.md [Optimistic-concurrency-control]: optimistic-concurrency-control.md [Set-validation]: set-validation.md [Videos]: videos.md [event-version]: event-version.md [INTERESTING-STUFF]: INTERESTING-STUFF.MD