Building Distributed Applications with Event-driven Architecture
summary
Covers concrete patterns and AWS tools: synchronous request/response versus asynchronous queues using Amazon SQS (at‑least‑once delivery), message routing with a bus via Amazon EventBridge (not idempotent by default but supports client‑provided idempotency keys), and orchestration with Step Functions (standard can wait up to one year, Express ~5 minutes). Explains duplicate sources (transmission, receiver, service), shows idempotency tokens persisted in DynamoDB and implemented with Lambda PowerTools, and demonstrates how these choices prevent double charges and improve resilience.
AI-written summary · about
chapters (13)
- 0:00Intro
- 4:08Agenda
- 4:51Enterprise integration patterns
- 8:02Synchronous request-response model
- 10:25Asynchronous pont-to-point model (queue)
- 16:42Asynchronous pont-to-point model (router)
- 18:52Asynchronous message-router model (bus)
- 22:11Event-driven architecture (EDA)
- 30:56Maintaining idempotency
- 32:36Where can duplicates occur?
- 35:01Building idempotent code
- 37:59Using services that are idempotent
- 42:52Outro
related talks
44mUnlocking Business Agility with Event-Driven Architectures
52mBest Practices in Event-Driven Application Design
31mImplementing distributed design patterns on AWS
38mEvent Design & Event-first Development
46mIntegration patterns & trade-offs for loosely coupled systems
55mServerless Design Patterns for the Enterprise with AWS Lambda
42mIntegration and Conversation Patterns in SaaS Applications
44mAdvanced Event-driven Architectures at