DEV Community

Discussion on: As a developer, do you even bother with containerisation?

Collapse
 
tbroyer profile image
Thomas Broyer

In the projects I work on, Java for the backend and JS for the frontend, we use containers for the side services (database, mailhog, etc.), driven by Docker Compose. This requires everyone to have the correct JDK installed (these days, either JDK 8 or 11, soon we'll probably add 17; on Linux it's easy to install JDKs side-by-side and switch between them) and the latest version of Node (either LTS or current; though we build with LTS for prod), which is generally the case.

Some of those projects are packaged as containers too for deployment, and that's our team's job to maintain the Dockerfile.

On a couple of legacy projects, we're still using old versions of Node, so we're using containers locally (rather than forcing everyone to use NVM.

Some other teams at work, using PHP on the backend, also use containers for running their code in development (code is bind-mounted into the container), as that allows them to use different versions of PHP, Apache (or Nginx), and Composer for each project.

On our build servers (Jenkins), everything is built inside containers so we don't have to install anything specific on the machines.