The Many Ways to Deploy Continuously
summary
Conference data shows 42% of customers practicing continuous deployment and reveals many concrete patterns not platitudes. Deploy strategies include prebuilt artifacts like Heroku slugs or AMIs, or machine self-updates via git; decentralized transfer (bit tar) cuts a 40 minute roll to 12 seconds. IMVU avoids locking by versioned tables, Facebook tolerates months of background migrations, GitHub requires merges that already ran in production, and feature flags plus metric-driven automatic rollbacks catch business regressions like the white‑on‑white buy button.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:30The Right Way
- 2:27Variables
- 2:59Deployment
- 3:44FTP
- 5:11The Race
- 6:39Heroku
- 7:51Schema Change
- 9:21ImVU
- 11:30No Table Locking
- 12:04Facebook
- 13:00Deploying Code
- 13:36Shipping an Image
- 14:48Empty Server
- 15:43Continuous Integration
- 17:42Web Servers
- 18:42Rolling Restarts
- 18:52Twitter
- 19:52New Shiny
- 21:04Continuous Deployment
- 21:26Monitoring Testing
- 22:40Facebook Similar Problem
- 23:14Monitoring
- 24:37Conclusion
related talks
23mContinuous Deployment - The Last Frontier for Continuous Delivery
32mHow Your Deployment Strategy Influences How People Code
31mFireside Chat: Continuous Deployment
41mAll Things Continuous
34mEnabling a Continuous Deployment Mindset
51mBetter software, faster: principles of Continuous Delivery and DevOps
41mSurviving Continuous Deployment in Distributed Systems
45mEnabling Continuous Delivery with Database Practices