Strangler Fig pattern
E684901
The Strangler Fig pattern is a software design and migration approach that incrementally replaces legacy systems by building new functionality around them until the old system can be safely retired.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Strangler Fig pattern canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7735580 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Strangler Fig pattern Context triple: [Martin Fowler, hasConcept, Strangler Fig pattern]
-
A.
"Implementation Patterns"
"Implementation Patterns" is a software development book by Kent Beck that distills practical coding techniques and design practices for writing clear, maintainable object-oriented code, particularly in Java.
-
B.
Strategy (design pattern)
Strategy is a behavioral design pattern that defines a family of interchangeable algorithms, encapsulates each one, and lets clients switch between them at runtime without changing their code.
-
C.
Handle-Body pattern
The Handle-Body pattern is a software design approach that separates an object’s public interface (“handle”) from its internal implementation and state (“body”) to enable encapsulation, flexibility, and easier maintenance.
-
D.
Pattern Hatching: Design Patterns Applied
Pattern Hatching: Design Patterns Applied is a follow-up book to the original Design Patterns that offers practical insights, case studies, and reflections on applying object-oriented design patterns in real-world software development.
-
E.
Design Patterns: Elements of Reusable Object-Oriented Software
Design Patterns: Elements of Reusable Object-Oriented Software is a seminal software engineering book by the "Gang of Four" that catalogues foundational object-oriented design patterns widely used in software development.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Strangler Fig pattern Target entity description: The Strangler Fig pattern is a software design and migration approach that incrementally replaces legacy systems by building new functionality around them until the old system can be safely retired.
-
A.
"Implementation Patterns"
"Implementation Patterns" is a software development book by Kent Beck that distills practical coding techniques and design practices for writing clear, maintainable object-oriented code, particularly in Java.
-
B.
Strategy (design pattern)
Strategy is a behavioral design pattern that defines a family of interchangeable algorithms, encapsulates each one, and lets clients switch between them at runtime without changing their code.
-
C.
Handle-Body pattern
The Handle-Body pattern is a software design approach that separates an object’s public interface (“handle”) from its internal implementation and state (“body”) to enable encapsulation, flexibility, and easier maintenance.
-
D.
Pattern Hatching: Design Patterns Applied
Pattern Hatching: Design Patterns Applied is a follow-up book to the original Design Patterns that offers practical insights, case studies, and reflections on applying object-oriented design patterns in real-world software development.
-
E.
Design Patterns: Elements of Reusable Object-Oriented Software
Design Patterns: Elements of Reusable Object-Oriented Software is a seminal software engineering book by the "Gang of Four" that catalogues foundational object-oriented design patterns widely used in software development.
- F. None of above. chosen
Statements (51)
| Predicate | Object |
|---|---|
| instanceOf |
application migration pattern
ⓘ
incremental modernization approach ⓘ software design pattern ⓘ |
| appliesTo |
API modernization
ⓘ
enterprise legacy systems ⓘ monolithic applications ⓘ on‑premise to cloud migrations ⓘ |
| benefit |
allows partial rollback if issues occur
ⓘ
enables phased rollout of new features ⓘ limits blast radius of changes ⓘ reduces need for full understanding of entire legacy system at once ⓘ spreads migration cost over time ⓘ supports parallel development of new system ⓘ |
| challenge |
can increase temporary system complexity
ⓘ
demands strong observability and testing ⓘ needs clear decomposition of legacy functionality ⓘ requires careful routing and integration design ⓘ |
| hasAlternativeName |
Strangler Fig application pattern
NERFINISHED
ⓘ
Strangler pattern ⓘ |
| hasGoal |
avoid big‑bang system replacement
ⓘ
enable continuous delivery during migration ⓘ minimize downtime during migration ⓘ reduce migration risk ⓘ replace legacy functionality with new implementation incrementally ⓘ |
| inspiredBy | strangler fig tree growth in nature ⓘ |
| keyIdea |
build new functionality around the existing system
ⓘ
coexistence of old and new systems during transition ⓘ retire legacy components once fully replaced ⓘ route traffic gradually from legacy to new components ⓘ |
| relatedTo |
anti‑corruption layer pattern
ⓘ
blue‑green deployment ⓘ branch by abstraction technique ⓘ canary release ⓘ facade pattern ⓘ microservices architecture ⓘ |
| typicallyInvolves |
eventual shutdown of legacy components
ⓘ
facade or routing layer in front of legacy system ⓘ incremental extraction of features from legacy system ⓘ monitoring and rollback mechanisms ⓘ progressive redirection of requests ⓘ |
| typicalStep |
decommission legacy endpoints once fully replaced
ⓘ
gradually reroute specific requests to new components ⓘ implement new functionality behind the facade ⓘ place a proxy or facade in front of the legacy system ⓘ remove the facade when legacy is fully retired ⓘ |
| usedFor |
application modernization
ⓘ
brownfield application development ⓘ gradual monolith to microservices migration ⓘ incremental system migration ⓘ legacy system replacement ⓘ risk‑reduced legacy decommissioning ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: Strangler Fig pattern Description of subject: The Strangler Fig pattern is a software design and migration approach that incrementally replaces legacy systems by building new functionality around them until the old system can be safely retired.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.