Incremental migration from legacy systems. Run old and new in parallel, gradually shift traffic, rollback at any point. Zero downtime, production-validated.
Gradually migrate critical systems with zero downtime. Use when replacing production systems requiring instant rollback and parallel validation. Routes traffic incrementally or swaps infrastructure components while running old and new systems simultaneously.
/plugin marketplace add adaptive-enforcement-lab/claude-skills/plugin install patterns@ael-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
examples.mdscripts/example-1.mermaidscripts/example-2.mermaidUse when:
Don't use when:
The strangler fig pattern has two distinct implementation approaches depending on what you're replacing:
Gradually shift user traffic from old to new system using percentage-based routing.
Use for:
How it works: Router/proxy directs percentage of traffic to new system. Start at 1%, increase gradually to 100%.
Replace entire components without routing traffic, including databases, service meshes, operators, and storage.
Use for:
How it works: Build new component, ensure compatibility, swap references, remove old component. No routing layer needed.
Key distinction: Traffic routing = gradual user migration. Component replacement = infrastructure swap with compatibility layer.
See examples.md for code examples.