Managing Asynchronous APIs
summary
Describes using AsyncAPI to declare channels, message schemas and protocol bindings, pairing it with CloudEvents for consistent event metadata and OpenTelemetry for runtime traces; shows generating code and infrastructure (React/Nunjucks templates + JS generator → Pulumi) to create topics/queues and scaffolding handlers; recommends schema registries (Confluent) to enforce forward/backward compatibility; reports this approach scales to ~2000 developers and hundreds of services and prevents failures like accidentally deleted queues by restoring declared subscriptions.
AI-written summary · about
chapters (16)
- 0:00Start
- 0:13Managing Asynchronous Apis
- 1:42Agenda
- 6:19Main Drum Design
- 9:58An Upstream and a Downstream Team
- 16:23High Cohesion and Low Coupling
- 19:33How Do I Discover these Endpoints
- 27:58Recap
- 32:49Info Object
- 39:57Tooling
- 40:59Commands and Events
- 44:18Types of Binding to Specific Protocols
- 46:10Forwards and Backwards Compatibility of Your Schemas
- 48:54Open Telemetry
- 50:11Parser and Generator Model
- 52:27Scaffolding
related talks
31mSpecify Your Asynchronous APIs with AsyncAPI
22mAsync API Specification 2.0
46mManaging Event Driven Architectures
23mBroadening the API Landscape: AsyncAPI and CloudEvents in the Enterprise
01h 03mOpenAPI and AsyncAPI, when to use which and why
28mEvent Driven API Management - Increase Reusability with AsyncAPI
22marmonizing Asynchronous Systems: NATS, CloudEvents and AsyncAPI.
31mAsyncAPI is here to stay