Course contentsShow
← Computer Science
Lesson 2390 of 2,87253. Agile and Software ProcessFree lesson

Continuous Delivery vs Deployment

Distinguishing between keeping code deployment-ready at all times versus automatically deploying every change.

Continuous Delivery vs Deployment

What you'll learn: You'll understand the crucial difference between keeping your code always ready to deploy versus automatically deploying every change that passes tests.

The Core Distinction

Both Continuous Delivery (CD) and Continuous Deployment share the same foundation: automated building and testing from Continuous Integration. But they differ in one critical decision point—who presses the deploy button.

Continuous Delivery

With Continuous Delivery, every code change that passes your automated tests creates a deployment-ready artifact. Your code could go to production at any moment—it's been tested, packaged, and verified. However, a human decides when to actually release it. This might happen daily, weekly, or triggered by business events (like a marketing campaign launch).

Think of it like a restaurant where every dish that passes quality control sits ready under the heat lamp. The head chef decides when to send it to the customer's table based on timing, coordination with other dishes, or special requests.

Continuous Deployment

Continuous Deployment takes this one step further: if your code passes all automated tests, it automatically goes to production—no manual gate. Every successful commit flows directly to users, often within minutes.

Using our restaurant analogy: the moment a dish passes quality control, it immediately goes to the customer. No waiting, no coordination—pure automation.

Why Choose One Over the Other?

Continuous Delivery suits scenarios where:

  • Business stakeholders need deployment timing control
  • Regulatory requirements demand manual approval
  • Coordinated releases with marketing or partners matter

Continuous Deployment works when:

  • You have extremely robust automated testing
  • Fast user feedback loops are critical
  • Your team culture embraces radical automation

Key Takeaway: Continuous Delivery keeps code deployment-ready with manual release decisions; Continuous Deployment automatically releases every change that passes tests—both require strong CI practices, but differ in their final automation step.