Bringing the Power of APIs to Event Driven Architecture
summary
Argues that adding APIs to an existing event hub turns an unruly EDA into a governable, secure platform by acting as an anti-corruption layer that publishes to topics, enforces auth/throttling, and does enrichment or polling on consumers. Presents an implemented framework: distributed event hub + lightweight domain APIs (front/back layers) that keep bounded contexts, avoid consumer-specific endpoints, and enable replayable logs and DDD-aligned separation. Claims this reduces regression testing and worked in large-company deployments.
AI-written summary · about
chapters (10)
- 0:00APIs in event-driven architecture
- 0:47Event-driven architecture defined
- 3:18APIs vs event-driven patterns
- 5:26APIs complement EDA
- 7:12APIs as anti-corruption layers
- 9:07Framework for APIs + EDA
- 11:37Domain-driven design and APIs
- 13:42Domain separation with APIs
- 15:51Domain API architecture best practices
- 17:18Q&A
related talks
32mUnifying API and event driven architectures
23mEvent API Products: Maximizing the Value of Your Event-Driven Architecture.
25mAccelerate Event Enabling the API Economy
26mAPI Management, meet Event Management
37mBuilding Event-driven Apps at Scale
28mHow APIs and Event driven architecture [...]
21mThe Future of Integration: from API to Event Meshes [...]
23mBroadening the API Landscape: AsyncAPI and CloudEvents in the Enterprise