AsyncAPI v3: Streamlining Event-Driven API Design
summary
AsyncAPI v3 serves as spec-as-config that autodeploys infrastructure and removes doc/implementation drift; demo converts an AsyncAPI HTTP spec and a Kafka spec into a working HTTP-to-Kafka bridge in minutes, where a curl POST appears as a Kafka message and a GET returns it. The open source project Zilla is a stateless, declarative multi‑protocol proxy with native Kafka/HTTP/MQTT/gRPC support, schema‑registry integration, security options (mTLS/SASL), and per-core engine scaling so runtime validation and autoscaling work in production.
AI-written summary · about
chapters (10)
- 0:00AsyncAPI and event-driven APIs
- 1:11Speaker and AsyncAPI role
- 3:43AsyncAPI power in EDA
- 5:09AsyncAPI adoption challenges
- 8:28Multi-protocol event systems
- 10:45Zilla for EDA streamlining
- 15:27Zilla production readiness
- 19:24AsyncAPI with Zilla demo
- 27:59AsyncAPI and Zilla resources
- 28:42Q&A
related talks
27mAsyncAPI & The future of API specs
39mIntroduction to AsyncAPI for Apache Kafka
31mAsyncAPI is here to stay
44mAsyncAPI – Swagger for asynchronous APIs
31mSpecify Your Asynchronous APIs with AsyncAPI
03mWhy AsyncAPI Is Essential for Modern Event-Driven Architectures
01h 03mOpenAPI and AsyncAPI, when to use which and why
23mBroadening the API Landscape: AsyncAPI and CloudEvents in the Enterprise