Notesfoundations🌱 seedling
Evolvability
Also: Extensibility · Modifiability · Agility · Expand and Contract · Strangler Fig
Evolvability is how easily a system can be adapted as requirements change. It comes from simplicity, small compatible steps and reversible decisions.
Why it exists
Requirements never stop changing: new features, regulations, platforms, scale and lessons learned. A system that can't change is replaced, usually painfully.
How it works
- Reversible decisions: "two-way doors" can be made fast; "one-way doors" (irreversible, consequential) deserve care. Design so most decisions stay two-way.
- Expand/contract (parallel change): add the new field, write both, migrate readers, then remove the old one, instead of one breaking change.
- Strangler fig: route traffic piece by piece from an old system to a new one rather than a big-bang rewrite.
- Evolvable data formats (Schema Evolution) that tolerate unknown fields and versions.
- Everything gets easier with less Accidental Complexity: you can only safely change what you understand.
Trade-offs
| Gains | Costs |
|---|---|
| changes ship continuously and safely | multi-step migrations take longer than one big change |
| old and new can coexist | temporary dual-write and dual-read code to maintain |
In practice
- Rolling upgrades depend on it: old and new versions must coexist (Rolling Upgrade).
Pitfalls
- Destructive migrations and unversioned public APIs: irreversible, so they turn every later change into a one-way door.
- Big-bang rewrites that must reach parity before delivering any value.
Connections
- Part of
- Maintainability
Recall
These cards are also in your review deck, scheduled with spaced repetition.