Transforming Legacy Systems: A DevOps Journey to Modernization

on YouTube ↗21m

" summary

Describes concrete modernization steps: VB6 maintenance example and a Windows Mobile (2001) UI color change took 10 days costing ~€12,000 to show hidden effort. Recommends module-by-module replatforming (eg. move DB to cloud), introduce APIs instead of rewrites, reuse open source, and phased refactor with CI/CD, containers, pipelines, monitoring and tracing. Highlights common pain: cleartext passwords, missing docs, slow feature velocity, and measurable cost/speed benefits from stepwise DevOps automation.

AI-written summary · about

" chapters (8)

1. 0:00Introduction and background
2. 3:03What is a legacy system
3. 7:07Problems with legacy systems
4. 10:22Strategies for modernization
5. 13:58DevOps role in transformation
6. 17:14Step-by-step modernization approach
7. 19:51Two key modernization strategies
8. 20:33Closing remarks and Q&A

" related talks

• 48mContinuous ModernizationEswaran Thandi · Global Software Architecture Summit 2022
• 58mModernizing your legacy applicationNico Vermeir · NDC Copenhagen 2025
• 14mDo Legacy Systems dream of Modernization?Katerina Andreadou · Voxxed Days Thessaloniki 2025
• 41mModernizing Legacy Apps - Platforms and StrategiesDino Esposito · Web Summer Camp 2024
• 45mDevOps Transformation — Breaking Down WallsKonstantin Pakulin · HighLoad++ 2017
• 43mAbout to Start Your Nth DevOps Transformation?Kalle Sirkesalo · DevDays || DevOps Pro || CyberWiseCon Europe 2025
• 23mDevOps and Legacy CodeOliver Hankeln, Peter Götz · DevOpsDays London 2019
• 58mSoftware ModernisationSandro Mancuso · JetBrains Technology Day for Java 2020