Demystifying ‘Event’ Related Software Concepts and Methodologies
summary
Defines events as immutable notifications and claims true event sourcing requires removing producer-side state so the event stream becomes the single source of truth; warns Kafka can hold streams but is inefficient long term for a high-volume append-only storage use case; specifies an event store must support sequential reads, targeted replays, snapshots, partitioning and archiving; contrasts event-carried state transfer with simple event notification; recommends Axon Server (event store + router) and Axon Framework (command/event/query buses) for implementation.
AI-written summary · about
chapters (8)
- 0:00Start
- 8:03Event Storming
- 11:05Event Modeling
- 19:03Event-carried State Transfer
- 22:40The Source Of Truth
- 28:50Event Store
- 37:58Message-driven
- 38:08Commands
related talks
01h 12mDemystifying "event-based" software concepts and methodologies
52mEvent-driven vs event sourcing: what's really the difference?
41mEvents! Events Everywhere!
51mThings I wish I knew before I started with event sourcing
48mEvent Sourcing - what could possibly go wrong?
43mEvent Sourcing dealing with an eventful past
01h 25mBuilding microservices with event sourcing and CQRS
58mLet's build the worst Event Sourcing system!