Exploring CI/CD practices

In the previous chapters, you learned how to design, build, and deploy a Gin web application on AWS. Currently, deploying new changes can be a time-consuming process. When deploying to an EC2 instance, Kubernetes, or Platform as a Service (PaaS), there are manual steps involved that help the new changes be pushed out of the door.

Luckily, many of these deployment steps can be automated, thus saving development time, removing possibilities for human errors, and reducing release cycle times. That's why in this section, you will learn how to embrace continuous integration (CI), continuous deployment (CD) and continuous delivery to accelerate the time to market (TTM) of your application, as well as to ensure high-quality features shipment through each iteration. But first, what do these practices mean?

Continuous integration

Continuous integration (CI) is the process of having a centralized code repository (for example, GitHub, Bitbucket, GitLab...