Modernizing your legacy application
summary
A 30‑year VB→VB.NET WinForms monolith becomes a phased modernization: a cloned and cleaned SQL database, ASMX replaced by REST Web API, frontend moved to Blazor WebAssembly, backend on ASP.NET Web API with a BFF, Azure Web Apps + Azure SQL and Azure AD, side‑by‑side VPN to keep print and 3 TB file store on‑prem. Project runs three years at 3 million euros, cuts seven modules to three, 70% deployed, Excel/VBA macros deferred for post‑MVP.
AI-written summary · about
chapters (12)
- 0:00The legacy system challenge
- 1:49Risks of maintaining legacy
- 3:40Modernization strategies
- 5:30Case study introduction
- 10:01The cost of technical debt
- 14:01Evaluating modernization paths
- 21:45The pre-study phase
- 28:06Functional and UX workshops
- 40:13Execution and trade-offs
- 43:38Architectural decision making
- 46:04Overcoming project challenges
- 55:35Key takeaways and conclusion
related talks
21mTransforming Legacy Systems: A DevOps Journey to Modernization
32mCold Case or Active Asset? A 2005 WinForms LoB Application
59mModernizing Legacy .NET Apps with Docker
53mPorting Code - Lessons Learned
41mModernizing Legacy Apps - Platforms and Strategies
49mFrom VB to Angular and Beyond Mastering Legacy Codebase Modernization
48mContinuous Modernization
49mContinuous Delivery for Legacy Code