Future of EDA Panel
summary
Panel argues EDA drives faster, decoupled delivery but surfaces concrete failure modes: wrong service boundaries and chatty back-and-forth cause fragility, and poor telemetry breaks debugging. Examples include a retrofit where events sent to Kafka retrofit recommendation system produced a working recommender, and AWS added EventBridge Kafka integration as a recent product move. Future work points to durable executions that give a sequential programming model over async infrastructure, GenAI accelerating junior devs, and business events directly driving auto-scaling.
AI-written summary · about
chapters (8)
- 0:00Intro
- 4:10How to get started with EDA its advantages
- 12:08When theory hits reality
- 19:30What are red flags with EDA?
- 23:40How does GenAI affect the developer's role?
- 31:25Which aspects of system integration will stay over time?
- 34:28The next big development in EDA
- 41:30Outro
related talks
41mFuture of EDA Panel
49mJourney to EDA: Patterns, Best Practices & Practical Tips
40mEDA Panel
49mEvolving Your Containerized REST Based Microservices to Adapt to EDA
49mFuture of Ruby Panel
28mXtremeJS Xperts Panel: The AI Revolution in Coding – Tools, Trends, and Tomorrow
31mClosing panel: The future of platform engineering and what to build next
46mPanel Discussion: AI's Impact on Developers