Our reading notes

Strangler Fig

Article by Martin Fowler

A gradual approach to modernizing legacy systems by replacing behavior in increments, with attention to why large replacement projects go wrong.

What to look for

01
Find a useful boundary where new behavior can coexist with the old system.
02
Question whether every existing behavior deserves to be rebuilt.

Keep in mind

Incremental replacement still needs a migration strategy and a way to retire the old path. The metaphor does not remove integration costs.

Put it to work

Try this next

Choose one business capability and sketch how it could move without requiring every user and dependency to switch at once.

Get the architecture template

Notes and exercises by Awesome CTO. The original work belongs to Martin Fowler.

Work through the bigger question.

Our architecture guide connects the reading to a practical approach and a template.