Patterns of Legacy Displacement

on YouTube ↗43m

" summary

Collaboration with Martin Fowler and James Lewis distills concrete patterns: avoid feature parity and big bang replacements (they push risk to the end and lock teams into 6–18 month release cycles); prefer Strangler/Vine approaches using event interception and change data capture (CDC) to incrementally move functionality. A retail case slices migration by product lines, discovers unprofitable SKUs and drops them, and builds new reporting first (parallel-run the critical aggregator). Call temporary components transitional architecture and throw them away once the new system proves it can release every two weeks.

AI-written summary · about

" chapters (8)

1. 0:00Intro
2. 2:00Why legacy happens
3. 4:41Agenda
4. 5:301. What are we trying to achieve?
5. 13:152. Breaking up the problem
6. 17:553. Delivery
7. 32:534. Organizational transformation
8. 42:16Outro

" related talks

• 47mLegacy Software: Really a Problem?Eberhard Wolff · Software Architecture Gathering – Digital 2023
• 43mBeyond Strangler Fig: Effective Patterns for Architectural ModernizationDavid Leitner · Craft Conference 2024
• 44mLegacy Software Really a ProblemEberhard Wolff · JCON WORLD ONLINE 2023
• 01h 01mLegacy Architecture Migration Patterns with DDDNick Tune · NDC Toronto 2026
• 47mRefactor Without Breaking Everything: Anatomy of Incremental Modernization PatternsHela Ben Khalfallah · Devoxx France 2026
• 43mLegacy Architecture Migration PatternsNick Tune, Guillaume Rahbari · Craft Conference 2025
• 54mThe Future of the Past – Legacy Will Stay With UsCarola Lilienthal · iSAQB Software Architecture Gathering – Digital 2021
• 40mLegacy Evolution – The Innovation Opportunity!Dave Thomas · GOTO Chicago 2018