11 ms·
Random remarks from the internet: The only reason I will mention containers this is because you are looking for a new solution and a new solution will result i
by brudgers 9y ago
Random remarks from the internet:
The only reason I will mention containers this is because you are looking for a new solution and a new solution will result in having to learn a new workflow anyway.
The advantage of putting multi-component configuration into a single container is that their deployment is atomic. The state of the remote machine is either:
Container not deployed
Container deployed
There are zero in between states of Partial-Deployment/Build that need to be either rolled back or rolled forward.
The issues created by the dependency of one container on another bubble up to the level of container orchestration but boil down to:
When container X.123 is deployed,
container Y.456 must be running.
If container Y.456 is not running,
deploy Y.456, then X.123.
Nothing gets built on the remote machine. No dependency gets pulled from another network. The container orchestration has the same logical problem of dependency management but far fewer practical issues with interrupted execution.