The Strangler Fig Pattern is a migration strategy for incrementally replacing a legacy system by gradually building new functionality alongside the existing system, routing traffic to new components as they become ready, until the legacy system is completely replaced—named after the strangler fig vine that gradually envelops and replaces its host tree.
Context for Technology Leaders
For CIOs, the Strangler Fig Pattern is the most risk-effective approach to legacy modernization, enabling continuous business operations while incrementally replacing legacy components. Enterprise architects use this pattern to avoid the high risk and long timelines of big-bang legacy replacement projects.
Key Principles
- 1Incremental Replacement: New functionality is built and deployed alongside the legacy system, replacing one capability at a time rather than attempting a complete system replacement.
- 2Traffic Routing: A routing layer (API gateway, proxy, or load balancer) directs requests to either the legacy or new system based on the functionality being accessed.
- 3Risk Reduction: Each increment is independently testable and reversible, dramatically reducing the risk compared to big-bang replacement approaches.
- 4Continuous Value Delivery: The organization receives value from modernized components immediately rather than waiting for a complete replacement to go live.
Strategic Implications for CIOs
CIOs should adopt the Strangler Fig Pattern as the default approach for legacy modernization, avoiding big-bang replacements except in rare cases where the legacy system cannot coexist with new components. Enterprise architects should design routing layers and data synchronization strategies that enable gradual migration.
Common Misconception
A common misconception is that the Strangler Fig Pattern requires a complete rewrite of the legacy system. The pattern allows selective replacement—modernizing the highest-value or highest-risk components while wrapping or retaining others indefinitely.