DEV Community

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

Collapse
 
thorstenhirsch profile image
Thorsten Hirsch • Edited

Yes, it's clearly one of the duties of the developers to build* a container, because they know their application the best, like the dependencies and how to scale the application. And in the end a container is a perfectly standardized delivery object for the ops guys.

(*) = The actual build of the container in the target environment is of course the job of the CI/CD pipeline. The developer's job here is to deliver a Dockerfile or whatever is required to build the container image.

However, I don't use a container for the code I'm working on during development. I'm not sure if auto-reloading, debugging, module installation, etc. can work in containers as well as outside containers at all, and it seems like it requires a lot of preparation in my development environment anyhow. So far I haven't seen the benefits of it and that's why I still develop my code outside of containers. But of course I install dependencies like Redis, MariaDB, messaging tools, etc. as containers.