# Deployment Strategy

> The plan for how a new version takes the old one's place on live servers.

**Field:** Software Development  
**Category:** DevOps & Cloud  
**Also known as:** Deploy Strategy, Release Strategy, Rollout Strategy

## Think of it like

Think of it like changing a tyre. You can stop the car, swap all four at once, or change one at a time.

## Definition

A deployment strategy is the plan for how a new version replaces the old one. The simplest stops the old version and starts the new one, with a short outage. Safer ones keep the site up the whole time. Some switch all traffic at once, and others move it a little at a time. The common ones are blue-green, canary and rolling.

## Example

Jack's team used to stop the site for five minutes each deploy. They switched to a rolling strategy, and users no longer see any break.

## Why it matters

It decides if users see an outage. It also decides how many meet a bug before you stop it.

## Common mistake

Picking the fanciest one for a small app. Rolling updates are often enough at first.

## Three principles

- **Old out, new in.** But how?
- **All at once or bit by bit.** The main choice.
- **Limit the blast.** Fewer users meet a bug.

## Related terms

- [Deployment (Software)](https://learn.benibix.com/term/development/deployment)
- [Blue-Green Deployment](https://learn.benibix.com/term/development/blue-green-deployment)
- [Canary Release](https://learn.benibix.com/term/development/canary-release)
- [Rolling Update](https://learn.benibix.com/term/development/rolling-update)

---

Source: https://learn.benibix.com/term/development/deployment-strategy
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-18
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
