Legacy Migration... Differently
summary
Presents an iterative alternative to full rewrites for legacy migration: identify small high‑change hotspots (e.g., a 30k‑line class actively modified) and implement small proxy adapters or API facades, deploy via continuous deployment, and measure impact. Uses a cash‑register → on‑prem → cloud migration example where adding a proxy reduced six months of integration toil, helped teams adopt changes, sped migration, and cut rework by preserving a stable core.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:11Legacy systems power
- 7:07System lifecycle & architects
- 10:21Code rewrite pitfalls
- 13:50Iterative modernization
- 16:40MVP for migration
- 18:45Legacy as business
related talks
43mLegacy Architecture Migration Patterns
47mLegacy Software: Really a Problem?
40mLegacy Evolution – The Innovation Opportunity!
47mRefactor Without Breaking Everything: Anatomy of Incremental Modernization Patterns
43mHow to Innovate in a Legacy
44mLegacy Software Really a Problem
48mLegacy, for lack of a better word, is good
27mLove Letter to Legacy