Strangler Fig Pattern

Introduction

Strangler fig pattern incrementally replaces monolith functionality by routing new or migrated paths to microservices while the legacy system still handles the rest — no big-bang rewrite.

The story

Ecommerce search lived in the monolith for 2 years while catalog extraction proceeded. Gateway routed /search/* to new Search Service; /legacy/* still hit monolith. Zero downtime; rollback was a routing change.

The business problem

Teams that skip disciplined Strangler Fig Pattern thinking pay in coupling, outages, and failed microservices interviews:

• Distributed ops: no tracing or health checks — hours to debug one checkout failure.
• Coupling: shared databases and libraries recreate monolith pain across the network.
• Deploy blast radius: one bad service deploy takes down unrelated domains.
• Team boundaries: services aligned to tech layers instead of business capabilities.

The problem teams faced

This lesson addresses:

• When and why Strangler Fig Pattern matters in decomposed architectures.
• How to define service boundaries and contracts under interview time pressure.
• Trade-offs vs alternatives — what staff engineers articulate in architecture reviews.
• Production patterns and failure modes in distributed systems.

Understanding the topic

Core idea: Strangler Fig Pattern in microservices architecture.

• Problem — distributed ops and coupling this topic addresses.
• Service design — boundaries, contracts, and data ownership.
• Trade-offs — sync vs async, consistency, deploy blast radius.
• Interview — how this appears in decomposition loops.

Internal architecture

Strangler Fig Pattern — microservices view:

Client → Gateway / Router
   ↓ path-based
   ├─ /api/v2/catalog/* → Catalog Microservice (new)
   ├─ /api/v2/search/*  → Search Microservice (new)
   └─ everything else   → Monolith (legacy)
   ↓ over time
Monolith shrinks; services grow

Visual explanation

Three diagrams: service architecture, decomposition process, and operational lens:

Informative example

Example — Strangler Fig Pattern:

Migration steps:
1. Identify vertical slice (e.g. product search)
2. Build service + DB + API parity
3. Dual-write or CDC sync during transition
4. Route traffic % canary → 100%
5. Remove monolith code path

Execution workflow

Real-world use

Netflix pioneered microservices at scale with hundreds of services and chaos engineering. Amazon's two-pizza teams and service-oriented architecture shaped modern decomposition. Uber migrated from monolith to domain-aligned services for independent deploys. Spotify uses squad-aligned microservices with internal platform tooling. These journeys inform every pattern in this course.

Production case study

Ecommerce search lived in the monolith for 2 years while catalog extraction proceeded. Gateway routed /search/* to new Search Service; /legacy/* still hit monolith. Zero downtime; rollback was a routi…

• Context: monolith pain or decomposition scenario from this lesson.
• Decision: service boundary and communication choices explained.
• Outcome: deploy frequency, incident isolation, or latency impact.

Trade-offs

• Pro: team autonomy and isolated failure domains.
• Con: distributed complexity — tracing, sagas, contract tests.
• Con: premature decomposition costs more than a modular monolith.

Decision framework

• Start modular monolith; extract when bounded context and team force are proven.
• Database-per-service — integrate via API and events, not shared schema.
• Document rejected alternatives — ADR or interview closing statement.

Best practices

• Align services to business capabilities, not technical layers.
• Draw sync vs async paths; propagate trace context on every hop.
• Health checks + readiness gates before traffic shift.

Anti-patterns to avoid

• Distributed monolith — shared DB, coupled deploys, synchronous chains everywhere.
• Nano-services — operational overhead exceeds team benefit.
• Shared libraries hiding domain coupling between teams.

Common mistakes

• Splitting before bounded contexts are clear — endless refactor.
• Cross-service transactions without saga or idempotency.

Debugging tips

• Follow one trace_id through the decomposition diagram.
• Ask "what couples these services?" for every sync call.

Optimization strategies

• Replace sync chains with domain events where latency allows.
• BFF to aggregate calls — don't make clients orchestrate services.

Common misconceptions

• Microservices ≠ always better — monolith wins for small teams and unclear domains.
• Interviews test decomposition judgment — not memorizing Netflix's service count.

Advanced interview questions

Summary

You can explain Strangler Fig Pattern in microservices interviews and production RFCs — with bounded contexts, data ownership, and resilience patterns. Teach it back without notes.