Event API Products: Maximizing the Value of Your Event-Driven Architecture.
summary
Argues that enterprises must treat bundles of related events as event API products and manage them with an event portal that discovers runtime events across brokers (Solace, Kafka, RabbitMQ, Kinesis), visualizes publish/subscribe relationships and dependencies, and exports AsyncAPI spec files. Presents five concrete steps — discover, assess, bundle, document, expose — and shows code generation to frameworks like Spring. Claims existing REST API portals don’t fit because events are push‑based via brokers, and that a dedicated portal scales better than DIY scripts.
AI-written summary · about
chapters (17)
- 0:00Event API Products intro
- 1:50Events vs APIs
- 3:16APIs vs events tech
- 5:01APIs evolving to events
- 6:45What is event API product
- 8:52REST + events real-time
- 9:54Design challenges EDA
- 11:175 steps to event API
- 13:01Scaling event API mgmt
- 14:04Solace Event Portal
- 16:31Visualizing Dependencies in Event-Driven Systems
- 17:13AsyncAPI Standard for Event API Documentation
- 17:54Solace PubSub+ Portal
- 18:16Summary and future
- 18:40Q&A: REST in EDA
- 20:06Q&A: Getting started
- 21:29Q&A: Biggest Misconceptions About Event APIs
related talks
25mEvent API Products – Maximizing the Value of Your EDA
34mMaximizing the Value of Your Event Driven Architecture
25mAccelerate Event Enabling the API Economy
28mEvent Driven API Management - Increase Reusability with AsyncAPI
29mAsyncAPI and Event API Products; a Match Made in Heaven
37mBuilding Event-driven Apps at Scale
26mAPI Management, meet Event Management
24mConnecting the World/Cities with Events Flows and APIs Interactions.