Loading content
An architectural pattern for incrementally replacing a monolith by routing functionality to new components step by step.
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.
Measures the percentage of traffic already routed to new components.
Time required to restore a stable state after a failed cutover attempt.
Observed error rates after incremental switching compared to the monolith.
An online shop extracts checkout and inventory into separate services to improve scaling and release frequency.
A booking platform moves payment logic and notifications sequentially into new services to minimize risk.
The frontend is extracted module by module from the monolith and integrated via gateway routing.
Analyze and prioritize functionality to extract
Build infrastructure for routing and observability
Incremental extraction, testing, canary rollouts and monitoring
Iteratively remove old monolith parts after stabilization