3 ms·
I've found the Docker discussion is seen through a better lense when you talk about the tech it's running. For polygot/hybrid cases where you have a smattering
by claytongulick 3y ago
I've found the Docker discussion is seen through a better lense when you talk about the tech it's running.
For polygot/hybrid cases where you have a smattering of different languages and supporting technologies/services, docker makes a lot of sense.
If you're all in (for example) on nodejs with a monorepo, it probably doesn't - you're just an "npm install" away from deployment.
Whenever I really dig into the docker passion, I usually find devs who are frustrated by having to manage a million little details to get the dev environment going.
If the language/stack takes that pain away, docker loses most of its value.
- dylan604 3y agomy issue is when my process can utilize 100% of CPU available, it makes no sense to have the ability to run several on the same VM. my VM is already one of several on the host. my software stack is already available on the AMI. I don't need the additional time to wait for my AMI to warm up and then warm up Docker. Once my AMI is up, I'm running