A fig and its host tree: the original image
The strangler fig pattern owes its name to a tree. In an article on his website (martinfowler.com, “Strangler Fig”, dated 22 August 2024, page checked on 12 November 2026), Martin Fowler recounts observing strangler figs in the forests of Queensland in 2001. The plant germinates in a crevice of a tree, draws its nutrients from the host, reaches the ground and the canopy, then becomes self-sustaining. The original tree may die, and the fig keeps its shape.
The author saw in this an analogy with the way his colleagues were modernising legacy software. His first post, kept on the site under the date of 29 June 2004, was titled “Strangler Application”. He explains that he later added the word “Fig” to the title: the shortened form “strangler” made people forget the botanical origin of the term and gave it a violent connotation.
Definition of the strangler fig pattern
The strangler fig pattern is the name given to the incremental modernisation of a legacy system. According to the article, it begins with small additions, for example new features, built on top of the old code but kept separate from it. Pieces of behaviour then move from the old system to the new code.
The pattern stands in contrast to wholesale replacement, whose pitfalls the author lists: the operation takes a long time while users are waiting for new features, the detail of existing behaviour is hard to establish, and part of that behaviour is no longer wanted.
Facade, seams and transitional architecture
- The facade. The descriptions of the pattern published by Microsoft (Azure Architecture Center) and by AWS (Prescriptive Guidance), consulted on the same day, place in front of the old system a facade, or proxy, that intercepts requests and routes them to the old system or to the new one.
- Seams. Martin Fowler’s article uses this name for the places where the system can be split into parts that can be replaced separately.
- Transitional architecture. The same article uses this name for the code that makes the two systems coexist and that disappears once modernisation is complete.
- Decommissioning. The old system is retired when nothing depends on it any more.
Strangler fig pattern, big-bang cutover, refactoring: not to be confused
A big-bang cutover replaces the old system in one go. The pattern spreads the replacement over stages, each of which puts part of the new system into service.
Refactoring changes the structure of code without changing its behaviour, within a single system. The pattern, for its part, keeps two systems running side by side and moves functions from one to the other.
Nor is the pattern a target architecture. AWS’s documentation presents it as a way of moving from a monolith to microservices; Martin Fowler’s article speaks more broadly of modernising legacy systems.
Illustration: an insurer’s claims management
Consider an insurer whose claims management application has to be replaced: a facade is placed in front of it and at first passes all requests through to it. Online claim reporting, a new feature, is built in the new system: the facade sends it the corresponding requests. Case tracking migrates next, then the calculation of settlements. When no request reaches the old application any more, it is switched off.
What the pattern costs, and the cases where it is a poor fit
Martin Fowler writes that this approach does not make the exercise easy: it makes the investment and its returns gradual and visible. The transitional architecture has a cost, which he considers offset by the reduction in risk and by value obtained earlier.
Microsoft’s documentation points out that the facade can become a single point of failure or a bottleneck. It also cites cases where the pattern is a poor fit, such as a small system that is simple to replace entirely.
Choosing this pattern among modernisation strategies, data coexistence and rollback for each stage are covered on our page on application modernisation.