COMPANY REFACTORING
summary
Legacy PHP4/MySQL4 monolith serves ~3M uniques/month with 2.4M LOC and peaks of ~3,000 reads/sec causing daily micro‑outages; code only runs on production over NFS so merges are manual and a hung copy can freeze all servers (NFS‑mounted monolith only runnable on production). Recovery uses Git, Capistrano deployments, convert key tables to InnoDB, upgrade PHP 5.3→5.4, add ElasticSearch and Symfony2; result: lines drop to ~600k, optimizer time 36h→4h and reads climb toward ~35k/sec, but layoffs and org changes follow.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:47Physical Situation
- 11:48Architecture
- 21:55Kill Script
- 23:27Critical Errors
- 25:41Github Version Control
- 41:02Software Architecture
- 48:28Adding a New Payment Method
related talks
40mModernizing the Legacy
40mRefactoring Huge Legacy PHP Applications - From 100 hours to minutes
55mModernizing Legacy Code - While Not Bringing Down Prod
32mQuietly Strangling the Monolith - a real-world migration of a high traffic monolith
54mTesting in Legacy: From Rags to Riches
42mSo You Want To Rewrite That...
47mModernising in Healthcare: a case study in decision making
30mTackling Technical Debt at Adobe: A Story