Considering future improvements

The Dockerfiles are pretty much duplicates, and there are some assumptions that can be parameterized. In the Kubernetes ecosystem, there are some interesting projects that help to address these concerns. Some of the solutions are for local development and can automatically generate the necessary Dockerfiles, while others are more targeted toward consistent and uniform production setups. We will look into some of these in later chapters. In this chapter, I want to keep it simple and avoid overwhelming you with too many options and layers of indirection.

Another opportunity for improvement is to test and build only services that have changed (or their dependencies have changed). As it stands, the build.sh script always builds all the images and tags them all with the same tags.

So far, we've built a complete CI pipeline using CircleCI and Docker. The next phase is to set up Argo CD as a continuous delivery pipeline.