Original Strangler Fig Application¶
Fowler, M. (2004). Original Strangler Fig Application. martinfowler.com.
Cited by¶
10 citations across 10 artifacts.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Strangler Fig Pattern
- The strangler fig pattern (named by Martin Fowler in 2004
This sourceFowler's bliki entry coining the 'Strangler Application' (now 'Strangler Fig Application') metaphor for incremental legacy replacement.
SupportedVerified against the source
- The strangler fig pattern (named by Martin Fowler in 2004
Mechanisms¶
- Categorical Refactoring Workflow
- Its strength is that it makes a frightening rewrite survivable: by staging the migration, validating each increment, and governing what lands, it converts "rewrite the tangle" into a sequence of small, reversible, checked steps — and it prevents the refactored model from rotting by attaching ownership as it goes.
This sourceUses gradual strangler-fig migration to reduce the risk of a wholesale legacy-system rewrite.
- Its strength is that it makes a frightening rewrite survivable: by staging the migration, validating each increment, and governing what lands, it converts "rewrite the tangle" into a sequence of small, reversible, checked steps — and it prevents the refactored model from rotting by attaching ownership as it goes.
- Consolidation Migration Plan
- The discipline is incremental cutover that strangles the old system gradually rather than replacing it in one leap,
This sourceDescribes gradually moving functionality from a legacy application into its replacement instead of relying on a single cutover.
- The discipline is incremental cutover that strangles the old system gradually rather than replacing it in one leap,
- Data Migration Runbook
- Runbooks pair naturally with a gradual strangler fig approach,
This sourceIntroduces the strangler-fig approach as gradual transfer of functionality from an old system to a new one.
- Runbooks pair naturally with a gradual strangler fig approach,
- Major Migration Approval Workflow
- Rather than a weekend "big bang," a major migration approval workflow sequences it: first internal test accounts, then employee accounts, then a single low-volume branch, then regions in waves, in the spirit of a strangler-fig migration that replaces a legacy system incrementally
This sourceDescribes gradual strangler-fig replacement of a legacy system from its edges.
- Rather than a weekend "big bang," a major migration approval workflow sequences it: first internal test accounts, then employee accounts, then a single low-volume branch, then regions in waves, in the spirit of a strangler-fig migration that replaces a legacy system incrementally
- Shadow Run or Parallel Run
- It is the highest-fidelity equivalence evidence available and the safe on-ramp to a risky cutover.
This sourceGradual coexistence and replacement can reduce the risk of a large cutover.
- It is the highest-fidelity equivalence evidence available and the safe on-ramp to a risky cutover.
- Stovepipe Retirement Migration Plan
- The guarding discipline is to gate every migration on the benefit metric, stage the coupling, and replace legacy incrementally with a strangler-fig
This sourceAdvocates gradual legacy displacement by growing a new system around the old and moving functionality incrementally, reducing the risk of a single cut-over rewrite.
- The guarding discipline is to gate every migration on the benefit metric, stage the coupling, and replace legacy incrementally with a strangler-fig
- Strategic Transition Map
- The staged, intercept-then-replace pattern it encodes is the strangler-fig approach to replacing a system incrementally rather than in one risky cutover.
This sourceDefines the strangler-fig approach as gradually moving functionality to a new system around the old instead of relying on a single cutover.
- The staged, intercept-then-replace pattern it encodes is the strangler-fig approach to replacing a system incrementally rather than in one risky cutover.
- Sunset or Replacement Plan
- A real, named approach is Martin Fowler's Strangler Fig pattern — incrementally growing a replacement around the edges of a legacy system until the old one can be removed.
This sourceNames the Strangler Fig approach and describes replacing a legacy application incrementally at its boundaries until the old system can be retired.
- A real, named approach is Martin Fowler's Strangler Fig pattern — incrementally growing a replacement around the edges of a legacy system until the old one can be removed.
- Taper and Handoff Plan
- The gradual, reversible ideal has a well-known software analogue in the strangler-fig pattern — replacing a system piece by piece while the old one keeps running until each new piece is proven
This sourceDescribes the strangler-fig pattern as gradually moving functionality from a legacy system into a new system until the old system is displaced.
- The gradual, reversible ideal has a well-known software analogue in the strangler-fig pattern — replacing a system piece by piece while the old one keeps running until each new piece is proven
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 1 of 10 citations: 1 supported. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:12bce75f5372 · see in the full table