Christian,
Yes, for JPM, which feels very long ago, I had a base image and then added only
an executable JAR as a new layer.
However, since I've seen the stats for porn sites on the Internet the size of
images got me a lot less worried :-) I've spent a lot of my working life trying
to make
Hi Peter,
I also thought a bit about how to possibly make the deployments smaller.
I see three possible solutions:
1. Put the main version of a system in a docker layer and upgrades in a
layer on top.
An example where this might make sense is Adobe Experience Manager. You put
the bundles of AEM
The basic idea of docker as well as k8s are immutable images.
The advantage of these is that you can give them a version and this way
uniquely identify what is running in the cloud at any time.
The upgrade process in k8s typically is that a new pod is installed with
the new docker image. As soon
I don't see any reason why upgrading your existing workflow with a static
Docker container and then updating the bundles would not work.
However ...
Just look at the number of moving parts that you then need in runtime. Creating
a Docker image in the build is trivial and deploying it to
