Unlocking the Power of Event APIs: Your Ultimate Guide
summary
Postman survey shows 85–86% of devs still use REST (down from 93% two years ago) and rising asynchronous styles; AsyncAPI and CloudEvents get practical roles: AsyncAPI for design‑time contracts while CloudEvents normalizes runtime payloads. Platform problem is clear: gateways lack event-native controls, so Gravitee.io demonstrates an event‑native API management pattern—example: Confluent Kafka → Gravitee gateway → webhook.site with JSON→XML transform, policies, filtering, replay and subscription approval.
AI-written summary · about
chapters (9)
- 0:00Event APIs introduction
- 2:33Postman API trends survey
- 5:03Sync vs async APIs
- 7:30AsyncAPI vs CloudEvents
- 10:25API management evolution
- 12:30Event-driven architectures adoption
- 15:39Event API mediation patterns
- 18:28Gravity’s event-native API management
- 22:39Summary
related talks
26mAPI Management, meet Event Management
24mConnecting the World/Cities with Events Flows and APIs Interactions.
23mEvent API Products: Maximizing the Value of Your Event-Driven Architecture.
27mAsyncAPI and the World Wide Flow
23mBroadening the API Landscape: AsyncAPI and CloudEvents in the Enterprise
32mNavigating Modern API Platforms: Insights & Strategies
25mAccelerate Event Enabling the API Economy
35mModern API Strategy: From Gateways to Event Mesh