The Dark Side Of Events
summary
Eight years at Internovus delivers concrete failure modes and fixes: publishing raw domain events causes logical, implementation and semantic coupling; switching many publishers from notification to event-carried state transfer removed duplicated projection logic; an event-sourced CRM needed synchronous command handling and the outbox pattern to avoid transactional loss; a new microservice became an architectural Trojan horse until an anti-corruption layer and boundary merges restored low global complexity.
AI-written summary · about
chapters (4)
- 0:00Start
- 5:55THE GOAL OF SOFTWARE ARCHITECTURE IS TO MANAGE COMPLEXITY!
- 10:55EVENT: CONTRACT FOR INTEGRATING SYSTEMS
- 18:13TYPES OF EVENTS
related talks
54mThe Dark Side Of Events
48m9 Fallacies of Event driven Architectures
56mEvents on the outside, on the inside and at the core
52mNavigating complexity in event-driven architectures: A domain-driven approach
30mUnhappy Path & Dealing with Bad Events
31mThe Power of Event-Driven Systems without Burning your Hands or Budgets
54mThinking in Events
55mNavigating complexity in event-driven architectures: A domain-driven approach