Opening the book…
To effectively manage numerous microservices and frequent releases, cloud-native development relies heavily on Continuous Integration (CI) and Continuous Delivery (CD) pipelines. These practices automate the building, testing, and deployment of software changes, ensuring that small incremental updates can be delivered to production quickly and reliably.
- Continuous Integration: Developers frequently merge code changes into a shared repository (often many times a day). Each change triggers an automated build and test process. Tools like Jenkins, GitLab CI, or GitHub Actions compile the code, run unit tests, and validate that the new changes integrate well with the existing codebase. CI aims to catch integration issues early by testing every change in isolation. With microservices, CI might mean running tests for each service independently, but also possibly running integration tests to ensure the services work together. Automated CI pipelines dramatically speed up development by ensuring code is always in a working state and by providing rapid feedback to developers when something breaks.
- Continuous Delivery/Deployment: Once changes pass CI, Continuous Delivery (CD) ensures those changes can be rapidly and safely deployed to production (or at least to a staging environment) at any time. In practice, CD pipelines automate the steps from packaging the application (for example, building a container image) to deploying it on the cloud infrastructure. This may include automated integration tests, user acceptance tests, or other validations in a staging environment, and then promotion to production. With proper CD, deployments become a routine, low-risk event rather than a large, infrequent ordeal. Many organizations strive for multiple deployments per day in a cloud-native setup.
A typical CI/CD deployment pipeline for a containerized microservice might work as follows: A developer merges code changes to the main branch, triggering the CI server (e.g. Jenkins) to compile code and run tests. If tests pass, the pipeline builds a new Docker container image for the service and pushes it to a registry (e.g. AWS ECR or Docker Hub). The CD process then deploys this new image to a staging environment (for instance, a Kubernetes cluster or a set of ECS tasks) where further tests or validations run. After automated health checks or perhaps manual approval, the new version is deployed to production, replacing the old version usually via a rolling update. All these steps happen with minimal human intervention.

In practice, many cloud providers offer managed CI/CD services or integrations (AWS CodePipeline, Google Cloud Build, etc.), and there are open source tools like Argo CD or Tekton for cloud-native CI/CD. The goal is always the same: automation. Embracing CI/CD is critical for cloud-native apps because it supports the frequent iteration and distributed nature of microservices – without automation, the operational overhead would be unmanageable.
This page titled 8.2.2: Continuous Integration and Continuous Delivery (CI/CD) was last modified on Tue, 22 Sep 2026 21:13:39 GMT and is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by Felix Amoruwa.
The book could not be loaded just now.