AsyncAPI and Event API Products; a Match Made in Heaven
summary
Claim: treat event APIs as products the same way REST APIs are packaged — use the AsyncAPI spec to define events, use tooling like PubSub+ Event Portal to catalog and distribute them, and follow five steps (discover, curate, bundle, release, manage). Example: an e‑commerce order system uses REST for customer calls and publishes inventory/shipping/fraud events; bundling those events into an event API product exposes pricing and analytics feeds to partners without revealing internal services, speeding integration and enabling reuse.
AI-written summary · about
chapters (6)
- 0:00Intro
- 1:17The Problem
- 6:19The Power of API Products
- 15:40Real World Use Cases
- 20:18Steps to Creating Event API Products
- 26:25Conclusion
related talks
28mEvent Driven API Management - Increase Reusability with AsyncAPI
23mEvent API Products: Maximizing the Value of Your Event-Driven Architecture.
31mAsyncAPI is here to stay
03mWhy AsyncAPI Is Essential for Modern Event-Driven Architectures
34mAPI Management, Meet Event Management
01h 03mOpenAPI and AsyncAPI, when to use which and why
23mBroadening the API Landscape: AsyncAPI and CloudEvents in the Enterprise
26mAPI Management, meet Event Management