One does not simply... rebuild a product
summary
Culture Amp rebuilds its nine‑year Performance product used by ~2,700 customers (largest 77k) because the domain model and two monoliths block scale to a $3B market; after chiseling debt and failed in‑place refactors the team burns down and rebuilds by slices, ships the Self Reflections first slice, freezes the old monolith, and measures wins: LCP 3.3s → 1.5s and backend deploy 40–60m → <5m, with few incidents and customer migrations succeeding.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:45The Problem
- 5:22Getting to the Point
- 8:39Reflections
- 11:21Product Radar
- 14:59Holistic Narrative
- 19:23Ground Rules
- 21:36Core Performance
- 25:11The Next Step
- 28:44Measuring Success
- 31:58Whats Next
related talks
26mOne does not simply... rebuild a product
14mGrowing pains: Scaling and re-architecting systems under fire
25mBreak up Monoliths and lay them to REST!
33mTaylor’s Guide to Big Rewrites
21mTaming Monoliths Without Microservices
38mFrom Monolith to Nimble
51mMicroservices and Microfrontends: Scaling, Learning, Growing
44mAvoiding the pitfalls of rebuilding software