The Many Meanings Of An AsyncAPI File
summary
AsyncAPI files represent either a concrete application or a class of apps depending on one-few-many and near-or-far tradeoffs; choose small, composable files for many similar services and larger documents for one-off apps. Solus builds Event Portal with two models—application vs event API—and lets teams download AsyncAPI via AsyncAPI Studio or expose Event APIs through a developer portal. Examples show cases where a producer plus two consumers produce three different AsyncAPI files, and the tooling supports that workflow in practice.
AI-written summary · about
chapters (10)
- 0:00AsyncAPI introduction
- 1:34What is an application
- 8:11Producer-consumer and brokers
- 13:05Big versus small AsyncAPIs
- 15:35One versus many applications
- 18:47Near versus far governance
- 24:08Event Portal domain model
- 27:56Building AsyncAPIs in Solus
- 31:06AsyncAPI design tips
- 32:53Summary and Q&A
related talks
01h 03mOpenAPI and AsyncAPI, when to use which and why
31mAsyncAPI is here to stay
03mWhy AsyncAPI Is Essential for Modern Event-Driven Architectures
31mSpecify Your Asynchronous APIs with AsyncAPI
29mAsyncAPI and Event API Products; a Match Made in Heaven
44mAsyncAPI – Swagger for asynchronous APIs
27mAsyncAPI & The future of API specs
07h 08mAsyncAPI online conference | #asyncapiconf