Evolution for Software Design and Architectures
Evolution is how a design changes safely over time instead of being rewritten. It covers incremental refactoring, the strangler fig approach of replacing a legacy system piece by piece, managing technical debt, feature toggles and database migrations, so a system can adapt while staying in production.
Stage: Practice · Part of the Software Design and Architecture roadmap · Last reviewed 19 November 2026
What to learn in Evolution
- Apply the strangler fig pattern to move a legacy feature
- Introduce a seam to test and replace tightly coupled code
- Roll out a change behind a feature toggle
- Apply expand and contract steps for a database schema change
- Track technical debt and schedule repayment alongside features
- Decide between refactoring and a full rewrite with evidence
Evolution interview questions
What is the strangler fig pattern?
You build new functionality around the legacy system and route traffic to it piece by piece, usually through a facade or proxy, until the old system has no remaining responsibilities and can be retired, avoiding a risky big-bang rewrite.
How do you change a database schema without downtime?
Use expand and contract: add new columns or tables compatibly, deploy code that writes both, migrate existing data, switch reads to the new structure, then remove the old one. Each step stays backward compatible with the running version.
Where Evolution fits in the Software Design and Architecture roadmap
Evolution belongs to the Practice stage (advanced level). Decide and evolve.
Other units in this stage
Back to the full Software Design and Architecture roadmap