Structure to Streams: Applying Full-Lifecycle API Management to ED Systems
summary
Argues that using AsyncAPI 3 plus an API gateway (example: WSO2 API Manager) turns Kafka/WebSocket streams into productized APIs: spec-first contracts generate SDKs and mocks, cut weeks from development, and make topics discoverable in a unified developer portal. Runtime proxies enforce OAuth2-based security, per-topic throttles and business plans (examples: 10,000 events per minute, 50,000 events/day), and perform protocol bridging. Approach augments existing brokers rather than replacing them and reports improved onboarding, visibility and reuse.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:08Async API management gap
- 3:36Async API pain points
- 7:10Event streams as products
- 10:22Contract-first with AsyncAPI
- 11:48Managing async streams
- 15:19Async API governance
- 18:12Proxying runtime governance
- 20:23Security for event APIs
- 21:51Developer portals
- 24:19API management overview
- 25:41Runtime enforcement
- 26:01Async governance takeaways
- 26:41Closing remarks
related talks
28mEvent Driven API Management - Increase Reusability with AsyncAPI
34mMaximizing the Value of Your Event Driven Architecture
29mAPIs and Event Streaming Dualty
21mStreamlining EDA: AsyncAPI-Driven Design, Documentation, and Testing
08mSimple Ways to Get Your Organization to Adopt AsyncAPI
22mAsync API Specification 2.0
19mAdopting AsyncAPI in Enterprisey Contexts
21mREST APIs vs. Data Streams: Which Is Right for Your Business?