Loading content
The Strangler Fig Pattern enables incremental modernization of legacy systems by developing new functionality alongside the monolith and progressively routing traffic to it. It reduces big-bang risks and supports incremental testing and releases during migration. Suitable for high-risk, complex replacements while keeping the system operational.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
The Strangler Fig Pattern replaces an existing system incrementally by building new capabilities alongside it and routing calls in a controlled way.
Martin Fowler named the pattern after the strangler fig that grows around a tree. It describes incremental modernization in which a new system gradually surrounds and replaces the old one.
A facade, router or adapter chooses per capability whether the monolith or new component responds. Each completed capability is tested, observed and routed permanently; the old part can then be removed. Transitional duplicate logic, data reconciliation and extra operational paths need active management.
A legacy system is replaced through small, reversible steps with new components.
Routing or a facade redirects individual capabilities from old to new.
Operations can continue; transition cost, data consistency and decommissioning need explicit planning.
The pattern helps plan risky modernization and turn a big-bang migration into verifiable increments.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.