DevOps and Lean in Legacy Environments
summary
Large legacy billing platform moves from 480 day lead times and six month releases to roughly three month cycles by reorganizing into cross functional feature teams, creating a shared delivery platform with Jenkins and the Atlassian stack and centralizing CI artifacts, instrumenting apps with deep telemetry (Stat Hub on alasta search ingesting ~1 billion events/day and 100,000+ trace points), practicing deployments in congruent environments ~70 times, cutting batch size to 14 week releases, and dropping impact score from 458 to 153 and recovery time from ~10 days to ~2 days.
AI-written summary · about
chapters (8)
- 0:00Transformation overview
- 10:45Operational congruency
- 12:16Application telemetry
- 14:33Work visibility and flow
- 17:32Automated deployments
- 18:45Cadence and synchronization
- 21:26Reducing batch size
- 23:36Results and future goals
related talks
31mFrom Legacy to ...
23mDevOps and Legacy Code
47mFrom bi-annual to fortnightly releases in 4 months for 15 teams and one monolith
51mContinuous Deployment for a Billion Dollar Order System
17mBeyond DevOps – Holistic transformations in uncertain times
25mDevOps & Insurance Company
01h 01mA team's transition to Continuous Delivery
34mEnabling a Continuous Deployment Mindset