Async API for Event Driven Architecture
summary
Explains how async APIs map to event driven architecture with clear choices: use a mediator when events require orchestration and conditional logic, or a broker for simple pub/sub; demos reference ActiveMQ and Google Pub/Sub as implementable transports. Covers event types (notification, event carry/changed-data, event sourcing), argues event sourcing stores a complete history (example: GitHub style), and warns of lost events, data-governance complexity and the need for an agreed AsyncAPI schema.
AI-written summary · about
chapters (4)
related talks
48mAsynchronous Web APIs in an Event Driven Architecture: when to use what
31mSpecify Your Asynchronous APIs with AsyncAPI
28mEvent Driven API Management - Increase Reusability with AsyncAPI
20mAPI Management for Event-Driven Microservices
46mManaging Event Driven Architectures
23mBroadening the API Landscape: AsyncAPI and CloudEvents in the Enterprise
27mAsyncAPI and the World Wide Flow
44mAsyncAPI – Swagger for asynchronous APIs