EDA Panel
summary
Panel reports enterprises using EventBridge as an EventBridge routing mesh to connect third‑party APIs, legacy mainframes and microservices, one migration hitting 5,000 tx/s, $1T processed after moving payments onto an EDA; observability remains hard so Step Functions-style visualisation is suggested; failed events are routinely kept in SQS DLQ and redriven; micro‑frontend migrations use vertical Strangler slices with routing at the edge via Lambda@Edge/CloudFront config; upskilling favors on‑the‑job bootstrapping and CoE support.
AI-written summary · about
chapters (12)
- 0:00Intro
- 3:50Cool things that are built with EDA
- 12:04Where is EDA not a good fit?
- 19:25Most interesting uses of AWS services
- 21:15UI integration
- 22:40Micro-Frontends
- 26:12Upscaling across a company
- 28:57Storage for failed events
- 31:30When to use a different architecture?
- 35:40Sensitive data
- 37:07Advice for writing a book
- 38:58Outro
related talks
41mFuture of EDA Panel
40mEDA Panel
49mEvolving Your Containerized REST Based Microservices to Adapt to EDA
49mJourney to EDA: Patterns, Best Practices & Practical Tips
40mEDA in Practice: Building an eCommerce Platform at
38mEvent-driven Architecture
44mAdvanced Event-driven Architectures at
41mGetting started with Orchestration and Choreography in Distributed Applications