Architecture Modernization: Aligning Software, Strategy, and Structure
summary
Modernization is worth doing when legacy systems slow product flow or let competitors win; expect surprises like 80% of legacy features unused and results such as ingestion processing time reduced by 80% after domain-aligned refactoring. Prioritize with impact mapping and Wardley mapping, discover hidden change coupling with event storming and CodeScene, and migrate incrementally using the Strangler Fig pattern, choosing first slices that deliver working value within 3–6 months.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:47Modernizing legacy systems
- 3:42When modernization becomes necessary
- 7:17Architecting for flow
- 14:22Modernizing beyond tech
- 18:10Modernization mindset tools
- 27:05Event storming for complexity
- 33:25Starting modernization
- 41:31Summary
related talks
48mArchitecture Modernization: Aligning Software, Strategy, and Structure
01h 12mArchitecture Modernization: Aligning Software, Strategy, and Structure
40mArchitecture Modernization: Aligning Software, Strategy, and Structure
40mArchitecture Modernization with DDD
15mHow to build a winning app modernization strategy & deliver on it
15mBuilding a Modernization Strategy
47mApplication Modernization: Renovating a House While You Live In It
30mHow to make better modernization decisions
