The Dark Side Of Events
summary
A team at Internovus rebuilds a sprawling monolith into microservices but finds events cause severe coupling, duplicated projection logic across dozens of subscribers, and a creeping distributed monolith; network unreliability and unordered delivery produce data corruption. Fixes include switching marketing and CRM to event-sourced/CQRS models, consolidating duplicate projections into event-carried state transfer APIs, using the outbox pattern to avoid transaction coupling, and merging or adding thin adapter layers where services require strong consistency. The result lowers global complexity and restores predictable behavior.
AI-written summary · about
chapters (10)
- 0:00Start
- 9:10Complexity Management
- 13:47ARCHITECTURE = BOUNDARIES DESIGN
- 15:40EVENT NOTIFICATION
- 18:31EVENT SOURCING / DOMAIN EVENTS
- 46:38BE PESSIMISTIC
- 47:32PRIVATE / PUBLIC EVENTS
- 51:12SOFTWARE ARCHITECTURE
- 51:41TYPES OF EVENTS
- 52:09LESSONS LEARNED
related talks
59mThe Dark Side Of Events
24mPatterns of Evolution from Monolith to Microservices
01h 03mMicroservices vs The Distributed Monolith
44mEvent-Driven Microservices, the Sense, the Non-sense and a Way Forward
23mMicroservices within a Monolith
47mEvent-Driven Microservices = Microservices Done Right
52mBuilding monolith applications that could scale to microservices..
36mThe Good, The Bad and The Ugly - An Event Sourcing Retrospective