Demystifying ‘Event’ Related Software Concepts and Methodologies
summary
Defines events as immutable notifications and shows how switching from storing state to storing changes lets you answer who, when and why; demonstrates event sourcing by rebuilding an aggregate from an event stream so the stream becomes the single source of truth; lists required event-store features: append-only storage, full sequential reads, per-aggregate snapshots to avoid replaying millions of events, and partitioning/archiving; contrasts event notification vs event-carried state transfer; shows a deployed stack: a message router plus an event store (Axon Server) and an HTTP bridge and framework providing command/query/event buses.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 2:13Store Changes
- 5:13Event
- 7:16Event storming
- 9:03Event modeling
- 11:59Eventdriven systems
- 13:58Eventdriven as a buzzword
- 15:03Eventdriven as a false claim
- 16:56Event notification
- 18:34Event card state transfer
- 27:24Sequential read
- 29:07Snapshots
- 31:04Partitioning archiving
- 32:58Passive aggressive events
- 36:42Message Router
- 38:55SecureS
- 41:56WorkSonic
- 44:23Action Framework
- 46:35More Information
- 47:32GeeCON Amsterdam
- 48:37Outro
related talks
01h 12mDemystifying "event-based" software concepts and methodologies
31mThe Power of Event-Driven Systems without Burning your Hands or Budgets
44mEvent Sourcing - You are doing it wrong
48mEvent-Driven Architecture – Benefits and Pitfalls
52mEvent Sourcing for the Cloud Developer
56mDeveloping Event-driven Microservices w/Event Sourcing and CQRS
46mEvent-Driven Microservices - not (just) about Events!
43mUnraveling the Threads: Event-Sourcing, CQRS, and Event-Driven Architecture