The core philosophy of a microservice environment must be based on the You build it, you run it (https://queue.acm.org/detail.cfm?id=1142065) model; that is, the team working on the microservice must own it end to end, right from development to deployment. The infrastructure required for the team to integrate, test, and deploy any changes must be completely automated. This makes it possible to build a continuous integration and continuous delivery (CD) pipeline, which is the backbone of microservices-based architectures.
The term CI/CD combines the practices of CI and CD together as a seamless process. In a typical microservices-based setup, the team continuously works on enhancing the features of the microservice and fixing the issues that are encountered in production.
The entire cycle from development to deployment has three major phases, as shown in the following diagram:
In the first phase, the team commits the changes to a version control repository...