My Monolith is Melting: Lessons from Legacy

on YouTube ↗28m

" summary

Claim: moved an SAP-led monolith from three releases a year that forced manufacturing stops to fortnightly releases with no downtime, cutting major/critical release incidents from nine or ten to zero in six months. Shows concrete steps: automate testing, get to infra as code or scripted deploys, introduce atomic versioning and APIs, use architectural decision records and incremental refactors. Focus is on measurable safety gains and gradual, test-driven modernization.

AI-written summary · about

" chapters (8)

1. 0:00Introduction
2. 3:11Legacy systems challenges
3. 6:20Change approval boards
4. 10:35Fix technology first
5. 14:26Incremental improvements
6. 19:43Cultural shifts
7. 25:07Handling legacy systems
8. 27:14Professional legacy management

" related talks

• 32mSplitting the monolithJimmy Bogard · LeadDev Austin 2019
• 43mContinuously deploying a distributed monolithVaidik Kapoor · Agile India 2021
• 23mDevOps and Legacy CodeOliver Hankeln, Peter Götz · DevOpsDays London 2019
• 33mFireside chat - Monoliths, Microservices & Modernization – Practical StrategiesIvan Brezak Brkan, Bruno Kovacevic · Infobip Shift 2021
• 23mOn the road from Monolith to MicroChristoph Moser · WeAreDevelopers Conference Vienna 2016
• 48mMicroMonolithMichal Franc · Codemotion Amsterdam 2017
• 47mFrom bi-annual to fortnightly releases in 4 months for 15 teams and one monolithThierry de Pauw · KanDDDinsky 2022
• 35mLiving in a Hybrid WorldCourtney Kissler · DevOpsDays Rockies 2016