Download to read offline
Uploaded byRobert Lemke
A practical introduction to Event Sourcing and CQRS
The document serves as an introduction to event sourcing and Command Query Responsibility Segregation (CQRS), outlining their significance in distributed event-driven architecture. It emphasizes storing all changes to a system rather than its current state, highlighting the immutability of events and the role of command handlers. Additionally, it mentions the Neos.eventsourcing framework as a helpful tool for implementing these concepts.
More Related Content
Similar to A practical introduction to Event Sourcing and CQRS
A practical introduction to Event Sourcing and CQRS
- 1. A practical introduction toEvent Sourcing and Command Query Responsibility Segregation
- 2. Robert Lemke CEO Flownative ProjectFounder Neos robert@flownative.com @robertlemke
- 3.
- 4.
- 5. Event Sourcing Store allchanges to the system, rather than it’s current state.
- 6. Event Sourcing Store allchanges to the system, rather than it’s current state.
- 7.
- 8. Motivation for EventSourcing
- 9.
- 10.
- 11.
- 12.
- 13. New representations /analysis
- 14.
- 15.
- 16.
- 17. Command Handlers will handlecommands. They don’t return a result, only accept or reject commands.
- 18.
- 19.
- 20. Domain Events: something interesting inthe domain / business
- 21. (infrastructure) events: user clicked button,log has been rotated, file upload failed
- 22. Events are something whichhappened in the past
- 23. You can’t changethe past, so events are immutable
- 25. Event Sourcing doesnot need a framework. But Neos.EventSourcing helps you implementing Event Sourcing with Flow.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33. Media / assets/ binary data
- 34.
- 35.
- 36.
- 37.