Strangling the dragon: modernizing legacy systems with the Strangler Fig pattern
summary
Describes using the Strangler Fig pattern to replace a legacy image service by incrementally moving functionality into a new job service, a small JavaScript service under 1,000 LOC that is fully emptied and decommissioned after about three years (finalized 2019). Combines Domain‑Driven Design and the Inverse Conway Manoeuvre to align teams, uses TDD and trunk‑based CI, and controls rollout with feature flags. Warns of over‑ambition, data duplication, the need for business buy‑in, and an expected short productivity dip.
AI-written summary · about
chapters (15)
- 0:00Legacy modernization intro
- 6:02Strangler Fig pattern
- 8:32Strangler Fig case study
- 12:08DDD for strangling systems
- 16:01Conway's law and teams
- 19:30Test Driven Development in modernization
- 23:49Strangler Fig vs rewrites
- 29:09Pitfalls and challenges of the pattern
- 33:30Getting started with Strangler Fig
- 37:24Summary
- 38:08Q&A: Avoiding Frankenstein systems
- 39:51Q&A: Business buy-in
- 40:55Q&A: Breaking down monoliths
- 41:59Q&A: Decoupling data models
- 44:34Q&A: Millennium project lessons
related talks
43mBeyond Strangler Fig: Effective Patterns for Architectural Modernization
43mPatterns of Legacy Displacement
24mModernise your monolith using strangler pattern
47mRefactor Without Breaking Everything: Anatomy of Incremental Modernization Patterns
15mBol.com and the Accelerated Legacy Challenge
30mApplication Modernization Using Cloud Strangler Pattern and DevOps Best Practices
37mStart with DDD when you have a monolith
23mArchitecture Remediation