Modernise your monolith using strangler pattern
summary
Shows how a Storefront monolith migrates incrementally using the Strangler Fig pattern on AWS by extracting inventory, order and card features into separate microservices (implemented as Lambda functions) with their own databases (RDS for legacy, DynamoDB for orders), an anti-corruption layer for transparent routing, a synchronising agent via event queues to keep the old DB eventually consistent, and AWS Step Functions for orchestration. Outcome: removes database contention, delivers millisecond responses at scale (millions of users), and lets the monolith be safely decommissioned.
AI-written summary · about
chapters (8)
- 0:00Modernizing monolithic apps
- 3:25The Strangler Fig pattern
- 5:16Identifying microservices
- 8:51Executing the migration
- 13:53Managing service interaction
- 17:05Workflow orchestration
- 18:31Data aggregation strategies
- 21:51Conclusion and resources
related talks
47mFrom Monolith to Microservices With the Strangler Pattern
30mJourney from monolith to microservices on AWS
30mApplication Modernization Using Cloud Strangler Pattern and DevOps Best Practices
58mModernizing an existing system to take a more domain-driven approach
01h 01mMonolith Decomposition Patterns
26mDDD + Microservices + DevOps – The Strangler Figs Way
43mMicroMonolith - Top anti-patterns of distributed systems
15mBol.com and the Accelerated Legacy Challenge
