What is Continuous Delivery and Deployment?
You'll learn the crucial distinction between two CD practices that often get confused: Continuous Delivery and Continuous Deployment.
The Core Difference
Both practices build on Continuous Integration (CI), but they differ in how far automation goes toward production:
Continuous Delivery means your code is always in a deployable state and automatically deployed to a staging or pre-production environment. However, the final push to production requires a manual approval — a human decision to release.
Continuous Deployment takes it one step further: every change that passes all automated tests is automatically deployed to production without human intervention. If the tests pass, it ships.
An Analogy
Think of a factory assembly line:
- Continuous Delivery = The product reaches the loading dock, fully packaged and ready to ship, but a manager must press the button to send the truck.
- Continuous Deployment = The truck automatically leaves the moment the product is packaged and quality-checked.
Why the Distinction Matters
Most organizations start with Continuous Delivery because:
- Regulatory requirements may demand manual approval
- Business stakeholders want timing control over releases
- Risk tolerance is lower initially
Continuous Deployment requires exceptional confidence in your automated testing, monitoring, and rollback capabilities. Companies like Netflix and Etsy practice this at scale.
Key Takeaway
Continuous Delivery automates deployment to staging with manual production gates; Continuous Deployment automates all the way to production with zero manual intervention. Both keep code always ready to ship, but differ in who (or what) pulls the final trigger.