Event-driven vs event sourcing: what's really the difference?
summary
Compares event-driven systems (real-time message passing for reactions) with event sourcing (persisting an immutable event stream as the source of truth to rebuild state by replay). Describes using EventStore and CQRS patterns, a postal scanning system (Notice X5) that stores and replays events for synchronization and offline recovery, and a restaurant simulation that contrasts choreography versus orchestration with a Process Manager; recommends snapshots, tracing and careful event versioning and uses Git and accounting as analogies.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:29Event Driven vs Event Sourcing
- 17:50Practical simulation
- 33:14Choreography vs Orchestration
- 41:24Versioning and complexity
- 47:46Adoption patterns
- 48:31Q&A
related talks
48mEvent Sourcing - what could possibly go wrong?
43mEvent Sourcing dealing with an eventful past
52mEvent Sourced Transformation in Financial Systems
49mDemystifying ‘Event’ Related Software Concepts and Methodologies
01h 07mAn Architecture with CQRS and Event Sourcing
01h 25mBuilding microservices with event sourcing and CQRS
30mDemystifying Event Sourcing: A Practical Approach to Modern Software Architecture
58mIntroduction to Event Sourcing