liveBook · Manning

Continuous delivery

Also called CD

Continuous delivery is a software practice that uses frequent, automated integration and validation to keep changes in a releasable state, ready for deployment.

How 2 Manning books explain it

Microservices Patterns, Second Edition

Continuous delivery is the practice of frequently integrating, testing, and deploying small software changes so that releases remain reliably deliverable.

How it is used
Reduces batch size within DevOps to support fast flow through frequent small changes deployed to production.
How deep it goes
Connects frequent small commits and pushes to testing and production deployment, without detailing pipeline implementation.
What you can do after
Apply via frequent small commits and pushes, testing each change and deploying it to production.

Read how Microservices Patterns, Second Edition explains continuous delivery →

Google Anthos in Action

A continuous delivery pipeline is an automated sequence of steps that builds, tests, and deploys software while keeping changes releasable.

How it is used
Automates the path from source changes to safe, sustainable production delivery across application, infrastructure, database, and resource changes.
How deep it goes
Defines delivery, contrasts deployment, and demonstrates a Cloud Run integration without detailing complete pipeline implementation.
Examples
Uses frequent integration, long-lived branch conflicts, and a Cloud Source Repositories–Cloud Build–Cloud Run deployment pipeline as examples.
What you can do after
Apply it via Cloud Source Repositories and Cloud Build to automate Cloud Run deployments and improve delivery reliability and visibility.

Read how Google Anthos in Action explains continuous delivery →

Also covered in

What to know first

Related concepts

Questions about continuous delivery

What is continuous delivery?

Continuous delivery is a software practice that uses frequent, automated integration and validation to keep changes in a releasable state, ready for deployment.

Which Manning books explain continuous delivery?

Microservices Patterns, Second Edition and Google Anthos in Action.

What should I know before learning continuous delivery?

Manning books that teach continuous delivery usually introduce automation first.

What is the difference between continuous delivery and long-lived branch?

Continuous delivery is a software practice that uses frequent, automated integration and validation to keep changes in a releasable state, ready for deployment. A long-lived branch is a version-control branch maintained for an extended period before its changes are integrated with other development work.

What kinds of continuous delivery are there?

Kinds of continuous delivery include continuous deployment.

What is continuous delivery a kind of?

Continuous delivery is a kind of continuous integration. Continuous integration is a software development practice of frequently integrating changes into a shared codebase and automatically validating them with builds, tests, or other checks.

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.