A conference talk transcript covering the Strangler Fig pattern as a safer alternative to full system rewrites for legacy modernization. The speaker explains why rewrites fail (moving targets, undocumented requirements, second system effect, complexity underestimation) and walks through a real-world example of gradually replacing a JavaScript image service over three years. The talk covers three complementary techniques: Domain-Driven Design for mapping the target architecture via bounded contexts, Conway's Law and the inverse Conway maneuver for aligning team structure with architecture, and TDD for ensuring safe incremental changes. Key pitfalls discussed include over-ambition, starting too many parallel tracks, insufficient time allocation, and working in long-lived branches instead of continuous integration. Feature flags are recommended for controlling cutover. The talk also addresses handling tightly coupled data models, avoiding Frankenstein architectures through continuous re-evaluation, and the need for business buy-in.
Sort: