AsyncAPI & The future of API specs
summary
Created three years ago because OpenAPI cannot express event-driven APIs, AsyncAPI defines event schemas, supports multiple protocols (MQTT, Kafka, WebSockets) and payload formats (JSON Schema, Avro), and ships a usable spec and tooling ecosystem that works but increases ecosystem fragmentation. Key proposals: specs as exchange format, official parsers and vendor adoption, tighter collaboration between OpenAPI/GraphQL/gRPC/RAML, and highly composable reusable specs so one flow (REST plus events) lives in a single, exportable document.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:15Why AsyncAPI
- 2:43About Fran Mendez
- 4:44The current landscape
- 12:45Users and companies
- 14:41Collaboration
- 22:00API specs inside specs
- 25:00API spec authors
related talks
22mAsync API Specification 2.0
03mWhy AsyncAPI Is Essential for Modern Event-Driven Architectures
31mAsyncAPI is here to stay
25mThe Future of API Specifications
44mAsyncAPI – Swagger for asynchronous APIs
30mAsyncAPI v3: Streamlining Event-Driven API Design
31mSpecify Your Asynchronous APIs with AsyncAPI
01h 03mOpenAPI and AsyncAPI, when to use which and why