AsyncAPI In Production
summary
AsyncAPI proves useful beyond docs: teams use it as infrastructure-as-code to generate Helm charts and Kubernetes CRDs that Strimzi applies to create Kafka topics, and as self-service portals (Bank of New Zealand style) that push Avro schemas to Confluent Schema Registry and eliminate Jira tickets. Companies run protocol-diverse deployments (Kafka, MQTT, WebSocket, SNS/SQS, Pulsar), apply Spectral linters for governance, generate models/clients/scaffolds (Adobe, Oracle, Adidas), and build event-centric developer portals (Event Catalog, Backstage); these automations cut manual ops, enable alerts/SLA monitoring, and control topic cost growth.
AI-written summary · about
chapters (14)
- 0:00AsyncAPI in production intro
- 3:01AsyncAPI landing page myths
- 8:36Industries using AsyncAPI
- 12:28AsyncAPI protocols
- 18:10AsyncAPI production use cases
- 19:33Infrastructure as code with AsyncAPI
- 23:01Self-service for events
- 24:49Governance in event systems
- 26:59QoS monitoring with AsyncAPI
- 30:51Cost control in events
- 33:39Code generation beyond docs
- 35:48Developer portals for events
- 39:45Why AsyncAPI investment
- 42:15Community and next steps
related talks
37mAPIs - Refactoring to Patterns
28mCode Generation For Enterprise Integration Patterns w/ AsyncAPI & ZenWave SDK
20mRevolutionizing API Management: Insights from an Architect
37mAPI Horror Stories from an Unnamed Coworking Company
24mAPI as the powerful EA lighthouse for a Composable Information System.
49mRethinking Reactive Architectures
32mPlatform Engineering for Software Developers and Architects (Redux)
24mAbstraction using APIs