« Previous 1 2
Building sustainably safe containers
Build by Number
Conclusions
The approach presented here does involve greater initial effort to keep the containers up to date in a fully automated way. In the sense of a continuous integration/continuous deployment pipeline, the applications also need to be tested with every new build to rule out incompatibilities from changes in the libraries.
For Spring Boot applications, the number of dependencies in the Java container is manageable. I have also containerized infrastructure services such as DNS in this way, although the number of containers required is greater. Nevertheless, automatic updating of the containers with this method has proven very useful in production operations.
« Previous 1 2
Buy this article as PDF
(incl. VAT)