Evolving Your Containerized REST Based Microservices to Adapt to EDA
summary
A containerized insurance claims demo shows how to move REST microservices to asynchronous EDA using EventBridge as event broker, SQS as an event store, Lambda and Step Functions for document workflows, and ECS Fargate or EKS for existing services. Document recognition custom labels and fraud checks fire events that trigger settlement and vendor flows; adding vendor service on EKS takes under two days with no core logic changes. Hexagonal adapters, CDK provisioning and KEDA for scaling prove the pattern works and narrows the fault impact radius.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 2:00Event driven architecture matters
- 3:23Traditional vs event driven
- 10:11Insurance claims use case
- 12:18Live demo: claims system
- 21:12Event broker deep dive: EventBridge
- 23:00Event compute with Lambda and SQS
- 24:26Document processing with Step Functions
- 25:49Adding containers to EDA
- 27:38ECS Fargate for EDA
- 28:19Event driven scaling with Kubernetes
- 31:14Demo with AWS CDK
- 32:17Benefits of event driven
- 33:18Polyglot architecture & integrations
- 35:08Key takeaways
- 36:59Reducing fault impact with EDA
- 37:20EDA patterns for data processing
- 38:47Scheduling ECS with EventBridge
- 39:31Scaling with DynamoDB & Kinesis
- 40:57Private endpoints & ECS scaling
- 42:02Hexagonal architecture for EDA
- 45:40Choosing services for API
- 46:46Summary
related talks
40mEDA Panel
01h 08mEvent Driven Architecture – Enabling Microservices
49mBuilding Next-Generation Applications with EDA
43mFuture of EDA Panel
36mKEDA: Event Driven and Serverless Containers in Kubernetes
39mMicroservices: Improving Team Management with Event Driven Architecture
41mGetting started with Orchestration and Choreography in Distributed Applications
46mOperating EDA with Quality in Mind
