The Road to Continuous Deployment: a Case Study
summary
Case study of a year and a half migration from a 10–15 year monolith for three Dutch job sites into a service‑oriented architecture using the strangler pattern and Docker (running on Docker 0.6), with Jenkins pipelines, Elasticsearch, and npm in the toolchain. Team of ~16 moves from manual weekend releases every 4–5 weeks to over 50 deployments per day, pipeline from commit to deploy under ten minutes, page loads drop from ~5–6s to under 0.5s and incidents fall dramatically using feature toggles and CI/CD.
AI-written summary · about
chapters (16)
- 0:00Start
- 7:12REFACTOR? REBUILD?
- 23:54BRANCHES ARE CHEAP?
- 25:10DELAYING INTEGRATION
- 26:06CONFLICTS
- 26:26FEATURE TOGGLES
- 28:06FEATURE TOGGLE DEBT
- 29:05CODE REVIEWS?
- 30:12PAIR PROGRAMMING
- 30:23CONTINUOUS INLINE CODE REVIEW
- 32:44100% CODE COVFEFE
- 34:34TEAM BUILDS IT
- 34:49TEAM IS RESPONSIBLE
- 36:11AUTOMATE REPEATABLE THINGS
- 36:36CONTINUOUS TESTING
- 40:33PIPELINE SPEED = KEY
related talks
49mThe road to continuous deployment: a case study
01h 02mThe Road to continuous deployment
34mEnabling a Continuous Deployment Mindset
43mContinuously deploying a distributed monolith
12mContinuous Deployment in a heavily regulated environment
26mHuman Trust in Continuos Deployment
01h 01mA team's transition to Continuous Delivery
54mFrom Code to Customer