3 ms·
> All of the dependencies of the application are bundled with the container which means no need to build on the fly on every server during deployment. This resu
by oconnore 10y ago
> All of the dependencies of the application are bundled with the container which means no need to build on the fly on every server during deployment. This results in much faster deployments and rollbacks. ... Not having to pull from git on every deployment eliminates the risk of a github outage keeping you from being able to deploy.
Obviously there are other benefits, but it's funny how much of the motivation for containers comes from "now we don't have to do git clone && npm install!", which was always the case.
- viraptor 10y agoEliminating running applications which talk over the network from deployment is a huge gain. Making things happen once rather than per-server is also a huge gain. On one server, cloning and installing things from the internet is all fine. Installing/upgrading hundreds at a time means you get to see how unreliable package management can be. You also have to guarantee enough bandwidth to the repo/package server to handle everything, or implement orchestration so servers don't install the same thing at the same time. At scale this matters.
- ThisIs_MyName 10y agolol people pull from github on every deployment? At the very least, you need a local mirror to prevent hogging the network when you're deploying to many servers.