Building next-gen applications with event-driven architecture
summary
Practical blueprint for event-driven apps: use order created events with at-least-once delivery, assign a stable item potency token (UUID) at the producer, and handle duplicates by storing results; prefer sparse events initially to avoid reverse-flooding, add fields intentionally, and accept the tradeoff of added latency for loose coupling. Use AWS primitives like SQS, SNS, EventBridge and Event Bus for queues/topics/filtering, Lambda Powertools for idempotency helpers, and Bedrock for GenAI-driven personalization; note up to 12.5 million subscribers as a scale example.
AI-written summary · about
chapters (6)
- 0:00Introduction and online shopping example
- 1:12Event-driven architecture basics
- 9:56Integration patterns overview
- 23:00Designing effective events
- 34:42Practical retail architecture demo
- 37:30Key takeaways and Q&A
related talks
41mGetting started with Event-Driven Architectures in 2023
52mSo You Want to Build An Event Driven System?
37mBuild next-gen applications with event-driven architectures
44mUnlocking Business Agility with Event-Driven Architectures
49mBuilding Next-Generation Applications with EDA
45mBuilding Event-driven Serverless Applications
56mDesigning Event-Driven Applications to Improve Scalability
47mPatterns for Building Event-driven Web & Mobile App Backends