Legacy Codebases are a DevOps Issue

on YouTube ↗26m

" summary

Legacy systems measurably slow development and inflate maintenance costs, so automation and incremental change win over big rewrites: using CI/CD pipelines, automated tests and vulnerability scans, and tools like SonarQube/SonarCloud lets teams refactor safely. Case studies show only about 37% of original code remains after five years, so clean-as-you-change is often cheaper than full cleanup. Deploying old and new apps in parallel behind an API gateway and comparing responses catches regressions while allowing gradual migration.

AI-written summary · about

" chapters (7)

1. 0:00Introduction
2. 2:48Legacy code pain points
3. 6:46Legacy code impacts
4. 9:53Refactoring case study
5. 16:16DevOps solutions
6. 21:49Legacy migration tips
7. 25:20Summary

" related talks

• 54mThe Future of the Past – Legacy Will Stay With UsCarola Lilienthal · iSAQB Software Architecture Gathering – Digital 2021
• 23mDevOps and Legacy CodeOliver Hankeln, Peter Götz · DevOpsDays London 2019
• 59mLiving with your LegacyJulie Lerman · Build Stuff 2019
• 47mLegacy Software: Really a Problem?Eberhard Wolff · Software Architecture Gathering – Digital 2023
• 41mLegacy, for lack of a better word, is goodUberto Barbini · JDD 2017
• 14mDo Legacy Systems dream of Modernization?Katerina Andreadou · Voxxed Days Thessaloniki 2025
• 48mLegacy, for lack of a better word, is goodUberto Barbini · Voxxed Days Bucharest 2018
• 26mDevOps and Lean in Legacy EnvironmentsScott Prugh · DevOps Enterprise Summit 2014 (San Francisco 2014)