4 ms·
> The use-case I need solved most often is the following: Create a standalone "server" that accepts and responds to network traffic, has some way to store data,
by audleman 10y ago
> The use-case I need solved most often is the following:
Create a standalone "server" that accepts and responds to network traffic, has some way to store data, and whose dependencies (i.e. system packages, frameworks, etc) I can manage independently of any of the other "servers" I have running.
SaltStack, Ansible, Chef are all configuration management tools that serve this purpose. They let you configure a standalone box any way you want.
The only use case I see for Docker over one of them is if you want to run multiple, independent services on one server. But why would you want to do that when you're running in the cloud? I don't see the benefit over separate instances, each tailored to be the exact size you need.
- icebraining 10y ago1) They let you be more fine-grained. Not all services need a full VM (even one of the small ones). 2) They let you have burstable instances, but controlling all the services sharing those resources, rather than being subjected to unknown neighbours. 3) Related to the previous points, they let you take advantage of free resources by distributing batch operations over VMs not under peak capacity.