The Dark Side of Events
summary
Catalogues concrete failures and fixes when events become coupling: duplicated projection logic across subscribers, unreliable delivery and ordering, and a surprising 200 event types exposed as public API. Converts the marketing and CRM subsystems to event sourcing and moves projection logic back inside the owning service, uses the outbox pattern to eliminate transactional coupling, and applies an anti-corruption layer/funnel context to stop Trojan-horse services. Result: fewer events, less global coupling, and improved UX via synchronous command results.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:52What is software architecture
- 8:28What are events
- 15:16Breaking the monolith
- 20:00The CRM
- 23:46Projections
- 26:46Trojan Horse
- 29:26Distributed Monolith
- 31:21Internobis
- 35:18Lessons
- 39:28Summary
related talks
56mEvents on the outside, on the inside and at the core
31mThe Power of Event-Driven Systems without Burning your Hands or Budgets
48m9 Fallacies of Event driven Architectures
30mHow Event Driven Architectures Go Wrong & How to Fix Them
46mManaging Event Driven Architectures
56mAn Abridged Guide to Event Sourcing
48mEvent Sourcing - what could possibly go wrong?
49mData Modeling in an Event Centric World