Journey to EDA: Patterns, Best Practices & Practical Tips
summary
Shows that naive EDA implementations quickly plateau into a “ball of mud” and offers concrete fixes: use event storming to find boundaries, treat messages as commands/events/queries, and apply patterns like point-to-point (SQS), pub/sub (EventBridge), and streaming (DynamoDB Streams). Demonstrates enrichment with EventBridge Pipes plus Lambda/Step Functions, large-payload handling via the claim check pattern (S3 + presigned URL), and reducing coupling with an anti-corruption/enricher layer. Recommends schema registries, an Event Catalog, and standards to retain agility as systems scale.
AI-written summary · about
chapters (7)
- 0:00Event-driven architectures intro
- 7:40Implementation vs behavior first
- 16:09Sync vs async communication
- 18:32Messaging patterns in EDA
- 25:12Integration pattern challenges
- 37:12Operating EDA systems
- 46:43Summary
related talks
52mSo You Want to Build An Event Driven System?
27mPatterns for Event-Driven APIs
55mNavigating complexity in event-driven architectures: A domain-driven approach
52mNavigating complexity in event-driven architectures: A domain-driven approach
54mSo You Want to Build An Event Driven System?
41mGetting started with Event-Driven Architectures in 2023
56mDesigning Event-Driven Applications to Improve Scalability
40mEDA Panel