Best Practices to Design & Build Event-driven Applications
summary
Covers concrete patterns and a runnable demo that wires Amazon EventBridge to Lambda functions and DynamoDB so an e‑commerce flow emits events, reserves inventory, calls payment and delivery, and records everything for debugging. Recommends one table per use case to document inputs, outputs and compensating actions (Saga pattern), enforces idempotency and schema compatibility, and shows custom event bus logging to DynamoDB plus CloudWatch, X‑Ray tracing, API destinations with rate limits and DLQ, and multi‑account/global endpoints.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:55Event-driven architecture design
- 3:50Agenda
- 4:38Intro to Amazon EventBridge
- 7:38How to design an event-driven application
- 20:18Demo
- 25:47Best practices for Amazon EventBridge
- 26:12Demo
- 30:09Best practices for Amazon EventBridge continued
- 36:18Summary
- 37:23Outro
related talks
26mEvent-Based API Patterns and Practices
40mBuilding Event Collection SDKs and Data Models
34mAPI Management, Meet Event Management
40mRefactoring to serverless
30mGolden pathways for cloud builders
49mMeasuring and increasing developer productivity with the help of Serverless
18mServerless Best Practices
39mBuilding Low-Code Applications with Serverless Workflows