>Docker based solution could probably cut it down to 5 mins.
this reminds me of when I was working on the Danish government electronic invoicing project.
The political driver of the project had made some statement along the line that a minute was going to be saved on every invoice sent (which I mean there would be millions and millions of minutes saved every month), and someone else made the observation in my hearing that he doubted that time saved would be monetizable. Which I took to mean that when small amounts of time are saved those are likely just swallowed by meaningless other tasks and not used effectively.
I doubt the 10 minutes saved per deploy by using Docker would be monetizable.
For our biggest app, Drupal, deployments are kind of hands on.
Dev(s) are waiting for the deployment, do some post deployment steps, check logs for any issues, make announcements, etc
and if we had to rollback, the easy solution is to find the previous deployment and run it again, speed would be probably be beneficial here
A) effort (aka 'man-hours'), or
B) duration (aka 'wall clock time')
?
launch vm: 1-2 min
config/deploy: 3-5 min (ansible)
create image: 2/3 min
launch new asg: 2-5 min
Containers greatly reduce most of these steps
This is one way to do it. (search Immutable Infrastructure)
For this application, traffic is quite stable so it doesn't come up often. But once or twice, we had some bug causing performance regressions.
They were not visible on the first day, but as usage grew over time the cluster started growing with the problem.
So it allowed the application to stay online (at an additional cost) until devs pick up the problem and have a solution ready, probably coming up in the following sprint only.
Config is inherited from the environment and cloud provider as the targets are Amazon Linux 2 based.
In addition to that, with cgroups and namespaces you get a lot of other benefits, which can be used with eg: systemd/etc but it's nice when one tool handles all of it.
My point is it is better to avoid the problem than employ a solution.
As other posters said, Docker largely exists to help with any situation where you don't have a single binary. These situations are still very common for many developers and devops engineers. And in those cases, Docker can be very helpful.
Something I'd take docker is: deployment speed.
Baking images and deploying new ASG makes production deployments take around ~ 15 min.
Docker based solution could probably cut it down to 5 mins.
Also more inclined to use a simpler/hands off service like ECS Fargate than straight kubernetes.
Also seems like over half the jobs being currently posted require k8s skills, might be difficult to avoid it for much longer