One Tool to Rule Them All
In the next chapter, I’ll show you examples of Dockerfile files for several development technologies. What I’d like you to note beforehand is that the processes we use don’t depend on the development technology. Whether Java, Python, .NET Core, Node.JS, PHP, or any other, the same instructions are used to build, ship, and deploy the applications.
This is a major benefit in many environments. If you’re part of a team, the chances are that many technologies are being used; however, the way to build, ship, and deploy the applications depends on the applications’ development tools. Having a single tool to manage them all yields several benefits:
Members of the team that use one development stack can help those using others.
A single CI/CD process and standard tools can be used across most projects, and improvements benefit all of those projects.
Practically, whatever the technology, the same instructions are used to build, ship, and deploy the applications. Something around those lines:
Build, deliver on the CI/CD server