Unlocking Business Agility with Event-Driven Architectures
summary
A concrete path from monolith to resilient, event-driven services: a prebooking use case shows queues and pub/sub replacing synchronous REST calls, removing location and availability dependencies and letting downstream services scale independently. Uses Amazon SQS (noting SQS hit 70M messages/sec peak), SNS/EventBridge for topics, and the topic-queue-chaining pattern plus correlation ID and return address for async request/response, enabling buffering, competing consumers, durable subscribers, and painless addition of new consumers.
AI-written summary · about
chapters (8)
- 0:00Introduction and housekeeping
- 1:33Event-driven architectures value
- 7:31Monolith to microservices challenges
- 13:56Synchronous vs asynchronous APIs
- 19:38Queues for resilience and scalability
- 29:33Adding components with minimal effort
- 37:58Pub/sub channels and topic-queue-chaining
- 42:14Summary and call to action
related talks
41mGetting started with Event-Driven Architectures in 2023
44mBuilding Distributed Applications with Event-driven Architecture
48mIntegration- and conversation-patterns for microservices
52mSo You Want to Build An Event Driven System?
30mApplication integration patterns for microservices
52mSo You Want to Build An Event Driven System?
39mBuilding next-gen applications with event-driven architecture
26mEvent Driven APIs