2 ms·
What's the advantage of switching to containers in this example setup? If you're only using ~3 machines, why not deploy "by hand" and have a text file that map
by dxhdr 11y ago
What's the advantage of switching to containers in this example setup?
If you're only using ~3 machines, why not deploy "by hand" and have a text file that maps containers to machines.
If you're using a ton of machines, presumably the marginal machine-waste is minimal and you should just stick to the role-per-machine setup. It's way simpler.
I'm questioning the necessity of all this added complexity.
- erez-rabih 11y agoThe advantages of switching to containers are numerous. They provide isolation, portability, quick boot times, consistency, application + dependencies in one package and a lot more. It totally refines development-production similarity when working on a software system. The same container that runs on the developer's machine will run in production. When working with Docker, your delivery pipeline is a lot more consistent and reflects better the code that runs on production later on. Docker has all the advantages VMs have, but with some major improvements: they are a lot more lightweight both on boot time and when moving them over the network, they share host machine resources and more. A quick search in Google will yield more than you can read about this topic :) I agree it is more complicated managing Docker containers than managing VMs, but I don't think of Docker as a new way to run things on production, this is just the side-effect. I think of Docker as a better, more consistent, way to develop and deliver software projects.