Event-Driven Microservices = Microservices Done Right
summary
Argues that replacing synchronous calls with events removes the distributed-monolith problem and restores isolation, autonomy and scalability by using concrete patterns: CQRS for separate read/write stores, outbox table + publisher-poller to atomically persist events and avoid lost messages, and Sagas (choreographed or orchestrated) for compensating workflows. Recommends Kafka or plain database-based messaging, at-least-once consumers with idempotency, and accepts eventual consistency; shows that these three patterns together let services evolve independently and keep business processes resilient.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:48Meet my co-presenter: Jens
- 2:03Systems Architectures over time
- 2:51The bad old Monolith
- 5:11From Monolith to SOA
- 7:09From SOA to Microservices
- 7:41Microservice Design Principles
- 13:38Take 1: Coupling
- 15:09Take 1: Evolution
- 16:37Take 1: Endresult: Distributed Monolith
- 18:24Which Principles were applied / violated?
- 20:15Alternatives?
- 22:29Take 2: The 'Event-Driven Way: Events as Notifications
- 27:40The top 3 Event-Driven Patterns
- 28:18Data Access in a Decentralized World
- 30:15CQRS Pattern
- 31:45CORS Flavors: CQRS in a single Microservice
- 34:06Repeat after Me
- 38:18Transactional Outbox Pattern
- 38:48Polling Publisher Pattern
- 40:21Coordination & Consistency
- 42:17Flavor 1: Choreographed Sagas
- 43:12Verdict Choreographed Sagas
- 44:16Flavor 2: Orchestrated Sagas
- 45:07Verdict Orchestrated Sagas
related talks
58mImplementing Event-driven Microservices
51mPatterns & Practices of Implementing Event-driven MicroSvc...
44mEvent-Driven Microservices, the Sense, the Non-sense and a Way Forward
46mEvent-Driven Microservices - not (just) about Events!
42mCreating event-driven microservices: the why, how and what
01h 08mEvent Driven Architecture – Enabling Microservices
57mEvent Driven Collaboration
56mDeveloping Event-driven Microservices w/Event Sourcing and CQRS