Strangler Fig Pattern

Normal Behavior

Incrementally replaces a legacy system by wrapping it with new services over time.

Failure Behavior

The replacement stops halfway, leaving the organization with two systems that both must be maintained.

Business Consequence

A stalled Strangler Fig Pattern leaves organizations permanently maintaining both the legacy monolith and the new microservices architecture. This doubles operational costs, fractures data models, and dramatically increases cognitive load for engineering teams, turning a modernization initiative into a permanent, highly complex technical debt disaster.

Visual Manifestation

"The API gateway routing table becomes a horrifying, thousands-of-lines-long regex nightmare, desperately trying to route traffic between modern REST endpoints and an ancient SOAP backend."

Satirical Behavior

"A migration strategy where you promise to rewrite the old system piece by piece, but inevitably give up halfway through, leaving future engineers to maintain two terrible systems instead of one."

Known Aliases

Technical Terminology

Failure Indicators