Asynchronous Web APIs in an Event Driven Architecture: when to use what

on YouTube ↗48m

" summary

Recommendation is to combine request/response APIs with event-driven APIs so UIs get real‑time updates while back ends stay scalable. Examples: stock tickers, live sports, notifications, collaborative editors; use an event broker like Kafka backbone for replay and fault tolerance, design for at-least-once with idempotent processing, and use CDC to migrate data incrementally instead of bulk batches. API gateway and developer portal coexistence is supported and AsyncAPI spec support coming in the next release.

AI-written summary · about

" chapters (14)

1. 0:00Intro
2. 0:50Are virtual conferences more inclusive for people
3. 3:40Introduction
4. 6:20Meet the speakers
5. 7:45API Manager
6. 16:05What if I lose one message
7. 18:30Examples in the financial insurance sector
8. 19:45How Ninja synchronous API is managed
9. 21:50Asynchronous API spec support
10. 22:22Why is asynchronous API tooling so late
11. 25:30How feasible is asynchronous for bulk data migration
12. 28:29How to decide which events to receive
13. 30:54Webhook pattern
14. 33:07Asynchronous APIs based on Kafka

" related talks

• 26mAsync API for Event Driven ArchitectureAna Borges · apidays Barcelona 2019
• 31mAsyncAPI is here to stayRolando Carrasco, Leonardo Gonzalez · AsyncAPI Conference 2021
• 31mSpecify Your Asynchronous APIs with AsyncAPISébastien Lecacheur · Devoxx France 2022
• 28mEvent Driven API Management - Increase Reusability with AsyncAPIBenjamin Gottstein · AsyncAPI Conference on Tour 2023 - Madrid
• 35mModern API Strategy: From Gateways to Event MeshSuresh Palaka · Apidays India 2025
• 23mBroadening the API Landscape: AsyncAPI and CloudEvents in the EnterpriseDaniel Kocot · AsyncAPI Online Conference 2024
• 01h 03mOpenAPI and AsyncAPI, when to use which and whyAri Hermawan · apidays LIVE Jakarta 2020
• 20mAPI Management for Event-Driven MicroservicesFran Méndez · apidays Helsinki 2019