DevOps and Legacy Code
summary
Practical steps for turning a brittle monolith into something operable: carve out services with the strangler pattern, migrate data using dual-write migration and queue-backed backfills, and add an incremental CI/CD pipeline so small changes build and deploy independently. Examples show replacing handfuls of hardcoded integrations with HTTP APIs, adding log aggregation and basic metrics to uninstrumented systems, and cutting deploy failures and manual rollback steps enough to run frequent, safe releases.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 1:39Legacy systems challenges
- 8:10Coupling in old systems
- 15:27Common sense interface
- 21:21Fixing the world overtime
related talks
26mDevOps and Lean in Legacy Environments
43mContinuously deploying a distributed monolith
49mThe road to continuous deployment: a case study
26mLegacy Codebases are a DevOps Issue
28mMy Monolith is Melting: Lessons from Legacy
34mYou only have to change one thing to do the DevOps
45mDevOps Transformation — Breaking Down Walls
05mAdventures In Enterprise: Lessons Learned Promoting DevOps In A Legacy Organization