liveBook · Manning

Progressive delivery

Also called progressive rollout, progressive deployment

Progressive delivery is a release technique that introduces a software change incrementally to expanding environments or user populations, allowing its behavior to be evaluated before broader release.

How 3 Manning books explain it

The Coder Cafe

A progressive rollout gradually expands the scope of a deployment across production environments.

How it is used
Reduces deployment risk in complex production systems by expanding change exposure gradually.
How deep it goes
Defines progressive scope expansion and contrasts it with feature flags, canaries, and shadow testing without detailing rollout procedures.
Examples
Uses large-scale production deployments spanning multiple clusters or regions as the primary rollout setting.
What you can do after
Apply it to reduce failure blast radius, increase change confidence, and support faster iterations.

Read how The Coder Cafe explains progressive delivery →

Microservices Patterns, Second Edition

A progressive deployment gradually exposes a newly deployed software version to increasing portions of production traffic.

How it is used
Uses gradual traffic exposure to deploy changes while old and new component versions run alongside one another.
How deep it goes
Places progressive deployment in a three-step rollout flow but does not detail traffic-splitting mechanics.
Examples
Uses a production-ready container image, registry, and overlapping old and new component versions.
What you can do after
Operate/configure a rollout by publishing a production-ready package, updating production configuration, and waiting for traffic-ready instances.

Read how Microservices Patterns, Second Edition explains progressive delivery →

Platform Engineering on Kubernetes

Progressive delivery is a release technique that gradually exposes a new application version while evaluating its behavior and controlling promotion.

How it is used
Guides teams toward controlled release strategies for experimentation and safer application delivery.
How deep it goes
Explains release patterns at a high level and reaches Kubernetes controllers, CRDs, plugins, promotions, and rollbacks.
Examples
Uses canary releases, Argo Rollouts resources, manual promotions, rollbacks, and a local KinD installation tutorial.
What you can do after
Operate/configure Argo Rollouts with kubectl, including controlled promotions, rollbacks, and dashboard access.

Read how Platform Engineering on Kubernetes explains progressive delivery →

Also covered in

What to know first

Related concepts

Questions about progressive delivery

What is progressive delivery?

Progressive delivery is a release technique that introduces a software change incrementally to expanding environments or user populations, allowing its behavior to be evaluated before broader release.

Which Manning books explain progressive delivery?

The Coder Cafe, Microservices Patterns, Second Edition and Platform Engineering on Kubernetes.

What should I know before learning progressive delivery?

Manning books that teach progressive delivery usually introduce canary deployment and deployment first.

What kinds of progressive delivery are there?

Kinds of progressive delivery include canary deployment.

What is progressive delivery a kind of?

Progressive delivery is a kind of delivery. Delivery is the process of making information, software, or software capabilities available to intended recipients or consumers.

What are the parts of progressive delivery?

Progressive delivery includes shadow deployment.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.