Building a Modernization Strategy
summary
Chubb faces a legacy estate (about 80% of systems legacy, ~200 billion lines) and reports modernization success rates around 24–39% with one in six projects becoming a “Black Swan.” The chosen path is gradual replacement using Chicken Little style gateways, building microservices with hexagonal architecture, and micro-frontends in a monorepo via NX Dev. The team implements adapters (REST/shop) to isolate domain logic, delivers one component at a time, and reports lower risk, faster feedback, and incremental business value rather than a single big‑bang replacement.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:46Legacy
- 2:23Legacy Systems
- 3:28Statistics
- 4:05Why does modernization fail
- 5:24Legacy vs modernization
- 6:01Gradual replacement
- 7:06Technical prerequisites
- 9:29hexagonal architecture
- 11:49micro front ends
- 12:38micr front ends
- 14:03conclusions
related talks
14mDo Legacy Systems dream of Modernization?
48mContinuous Modernization
48mArchitecture Modernization: Aligning Software, Strategy, and Structure
30mModernization: Taming the legacy and keeping the new house clean
48mArchitecture Modernization: Aligning Software, Strategy, and Structure
59mArchitecture Modernization Anti-Patterns: The Cost of Good Intentions
01h 00mHow to Make Better Modernization Decisions
47mApplication Modernization: Renovating a House While You Live In It