Delivery vs Deployment

"Continuous delivery" and "continuous deployment" sound like the same thing said twice. They even share the same initials — CD — which is why people use them interchangeably and quietly confuse each other. But they name two different things, and the gap between them is the single most useful distinction in this chapter.

Here is the whole difference in one sentence: continuous delivery keeps every change ready to release at the push of a button, and continuous deployment removes the button. One leaves a human in charge of the final "go"; the other lets the machine push it out the moment the tests pass. Everything else in this topic is just that idea, looked at from a few angles.

What is continuous delivery?

Continuous delivery means the app is always ready to release. Every change Maya merges is automatically tested and built into a finished, shippable package, then parked at the door — proven, and waiting. Nothing is half-done or in an unknown state.

But it does not go out on its own. A person — Sam, or whoever owns the release — looks at it and presses the button to send it to readers. The work of preparing a release is fully automated; the decision to release is still a human one. That human-held button is the defining feature of delivery.

What is continuous deployment?

Continuous deployment takes that exact setup and automates the final step too. When a change passes every test, it deploys itself to real users — no button, no waiting, no person in the loop for that last move. Maya merges a fix in the morning and readers can be using it minutes later.

This sounds reckless until you see what holds it up. Because no human inspects each release, the automated tests have to be trusted completely — continuous deployment needs *more* testing discipline than delivery, not less. The safety moved from a person's judgment into the test suite.

The single difference

So the two are the same pipeline with one thing changed: whether a human approves the final release, or the machine does it automatically. Between the two terms, that is the whole difference. Continuous delivery stops one step short of users and waits for a person; continuous deployment runs all the way through.

Think of two ways to send out packages. Continuous delivery is a loaded delivery truck, fully packed and ready, idling until the driver decides to pull out. Continuous deployment is a conveyor belt that carries each package straight out the door the instant it's sealed. Same packages, same loading — the difference is only whether a person says "now."

Both stand on CI

Neither one works without the step before it. Back in Chapter 4, continuous integration made every change get tested and built automatically the moment it was written. Delivery and deployment are what happens to that tested, built result next — they pick up exactly where CI leaves off.

That is why you so often see the three letters together as "CI/CD." CI gets each change verified and packaged; CD gets it released. You cannot safely auto-release something you haven't first auto-tested, so CD extends CI rather than replacing it — the build half and the ship half of one pipeline.