The Strangler Pattern (also known as the Strangler Fig Pattern) is an application modernization strategy that incrementally replaces components of a legacy system with new implementations, gradually migrating functionality until the legacy system can be fully decommissioned.
Context for Technology Leaders
For CIOs and enterprise architects, the strangler pattern is one of the most practical and low-risk approaches to legacy system modernization. Named after the strangler fig tree that gradually envelops and replaces its host tree, this pattern avoids the high risk of big-bang rewrites by allowing organizations to incrementally migrate functionality. Each increment delivers immediate value while reducing dependency on the legacy system. It is particularly effective when combined with an API layer or facade that routes traffic between legacy and new implementations.
Key Principles
- 1Incremental Migration: Replacing legacy functionality in small, manageable increments rather than attempting a complete rewrite, reducing risk and enabling continuous value delivery.
- 2Facade Layer: Introducing a routing layer (often an API gateway or facade) that directs requests to either the legacy system or the new implementation based on migration progress.
- 3Coexistence: Legacy and new systems run simultaneously during the migration period, with clear boundaries and integration points between them.
- 4Progressive Cutover: Gradually shifting traffic from legacy to new components, with the ability to roll back individual migrations if issues arise.
Strategic Implications for CIOs
The strangler pattern is strategically important for CIOs because it de-risks modernization by enabling continuous delivery of value while avoiding the existential risk of big-bang replacements. It allows organizations to modernize at a pace that matches their capacity and budget. Enterprise architects design the facade layer and define the migration sequence, prioritizing components based on business value and technical complexity. For board communication, the strangler pattern demonstrates a disciplined, risk-managed approach to legacy modernization with measurable progress milestones.
Common Misconception
A common misconception is that the strangler pattern is only suitable for web applications with HTTP-based routing. In reality, the pattern can be applied to any system where functionality can be incrementally redirected, including batch processing systems, message-based integrations, and database-driven applications.