OpenAPI and AsyncAPI, when to use which and why
summary
AsyncAPI is presented as “Swagger for messaging” with a working toolchain: Solace Event Portal hosts an order.created event schema, an AsyncAPI spec (v2) generates a skeleton via the spring cloud stream generator, and a cloud broker (Solace) accepts a published JSON payload and delivers it to subscribers in the demo. Use cases: slow downstreams (eventual consistency), protocol bridging (JMS/MQTT/WS), and fan‑out dashboards across an event mesh with hierarchical topic routing and wildcards.
AI-written summary · about
chapters (15)
- 0:00Start
- 7:54Introduction about Async Api
- 9:55Async Api
- 12:01Why Do We Need Async Api
- 13:31Tight Surface Coupling
- 25:38Eventbroker
- 26:39Event Broker
- 27:33Soa plus Messaging
- 30:11Event Mesh
- 31:16Routing
- 34:57Eventual Consistency
- 37:34Demo
- 39:38Real Time Dashboard
- 48:20Async Api Generator Command
- 52:50Which Protocol You Prefer Based on Performance
related talks
44mAsyncAPI – Swagger for asynchronous APIs
22mAsync API Specification 2.0
31mAsyncAPI is here to stay
21mUsing the AsyncAPI Ecosystem for your Event-Driven Architecture
03mWhy AsyncAPI Is Essential for Modern Event-Driven Architectures
31mSpecify Your Asynchronous APIs with AsyncAPI
23mBroadening the API Landscape: AsyncAPI and CloudEvents in the Enterprise
27mAsyncAPI & The future of API specs