Event-Driven Microservices, the Sense, the Non-sense and a Way Forward
summary
Argues that events fit specific roles not everything — distinguishes event notification, event-carried state transfer, and event sourcing and recommends starting with a monolith then extracting components for non-functional reasons (CPU, memory, team focus). Advises using an event store plus CQRS with projections for queries, anti-corruption layers and bounded contexts to avoid global “marriages,” and upcasters for evolving events; cites Axon as an off‑the‑shelf event store/tool. Calls out noun-driven service design as a common anti‑pattern.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:58Once upon a time...
- 3:29Microservices to the rescue!
- 3:40Why microservices?
- 5:17Order Service
- 12:27"Event" all the things!
- 12:54Maslow's Hammer
- 13:11Maslow Syndrome
- 13:55Event-carried State Transfer
- 30:28"CQRS" all the things?
- 35:33In closing....
- 35:54Sharing is caring
- 36:10Beware coupling across bounded contexts
- 36:24Microservice Journey
- 36:35wax-on, wax-off!
related talks
46mEvent-Driven Microservices - not (just) about Events!
47mEvent-Driven Microservices = Microservices Done Right
58mImplementing Event-driven Microservices
31mThe Power of Event-Driven Systems without Burning your Hands or Budgets
01h 25mBuilding microservices with event sourcing and CQRS
56mDeveloping Event-driven Microservices w/Event Sourcing and CQRS
52mBuilding monolith applications that could scale to microservices..
54mDemystifying ‘Event’ Related Software Concepts and Methodologies