Managing Event Driven Architectures
summary
Claims that documenting event endpoints fixes scale problems and shows how to do it: use AsyncAPI (and CloudEvents) to describe channels, bindings and message schemas, then run a parser + generator to AsyncAPI documents channels, bindings, messages and produce handler scaffolding and infrastructure. Demos show VS Code and AsyncAPI Studio, Spectral linting, Backstage cataloging and a Cupid-style generator that generators scaffold code and infra to create topics/queues, ACLs and deploy runtime. Notes pub/sub vs point-to-point confusion and forthcoming spec fixes; shows end-to-end code generation and deployment.
AI-written summary · about
chapters (14)
- 0:00Start
- 4:43Endpoint Discovery
- 8:32Endpoints
- 10:10Domain Driven Design
- 11:53Bounded Context
- 15:21Anti-Corruption Layer
- 18:25Necessary Coupling
- 26:01Async Api
- 30:06Components
- 30:26Extension Points
- 32:28Publish and Subscribe
- 37:17Async Api Studio
- 38:42Cupid
- 39:30React Template
related talks
39mEvent Design with AsyncAPI, DDD, and AI
57mManaging Asynchronous APIs
28mEvent Driven API Management - Increase Reusability with AsyncAPI
31mSpecify Your Asynchronous APIs with AsyncAPI
34mMaximizing the Value of Your Event Driven Architecture
23mEvent API Products: Maximizing the Value of Your Event-Driven Architecture.
41mOpen Standards for Building Event-Driven Applications in the Cloud
25mEvent API Products – Maximizing the Value of Your EDA