Through the 2000s, releasing a new version of a website was an event: engineering teams bundled weeks of changes into a single push, scheduled downtime for it, and treated deploy day as the moment everything could break at once. Etsy ran this way too, with a dedicated deployment team acting as gatekeeper and late nights whenever a bundled release went wrong, because nobody could tell which of dozens of simultaneous changes had caused the failure.
The standard fix for fragile releases was more process before the release — longer QA cycles, more sign-offs, bigger staging environments — which added delay without removing the actual risk: a release still shipped forty features at once, so a single bug still forced engineers to either roll back everything or hunt through the whole batch under pressure to find the one line at fault.
Continuous deployment: tens of small production deploys a day, each trivially attributable and reversible, replacing feared release nights.
Shrank release batch size to one or a few changes per deploy, making each failure trivially attributable and cheap to undo, instead of adding more pre-release process.
Large bundled releases bury any single bug among dozens of changes, making attribution slow and costly.
Small batches mean each deploy has at most one plausible cause, so failures are instantly traceable.
Small changes are individually reversible, so a bad deploy can be undone without rolling back everything.
Frequent small deploys spread risk across many low-stakes events, reducing fear and encouraging even smaller batches.
When failures are hard to diagnose, shrink the batch size instead of adding more process before release.
By mid-2010 Etsy's own engineering leadership reported roughly 200 production deployments a month and rising ("204 production deployments in July, about 30% more than June"), each small enough to trace to one engineer; by 2014 the company was publicly citing about 30 deploys a day.
FOLLOW THE EVIDENCE
The sources
- Scaling startups Chad Dickerson (Etsy CTO, personal engineering blog) · blog.chaddickerson.com
- The Future Workplace Is Now: How Etsy Makes 30 Innovations Per Day Forbes · forbes.com