3 ms·
So many people say that but if you can't scale anything stateful what is the point of all of this. Often it is the database that needs to scale the most since
by dpeterson 11y ago
So many people say that but if you can't scale anything stateful what is the point of all of this. Often it is the database that needs to scale the most since business applications spend a lot of time there and much less time actually performing cpu intense calculations. I do work for a very large organization that can afford mongodb as a service but for startups without large sums of money, 1400 dollars per month for amazon to run mongodb or 1000 a month for mongolabs to do it seems high. Plus, I want to colocate my data with my apps to limit latency. It just seems like "running stateful services in containers is a bad idea" is parroted over and over because its such a hard problem few people seem capable of solving. Instead they spin up 1000 stateless containers that print hello world and become impressed with themselves.
- cpuguy83 11y agoIndeed. This is why we've developed the plugin ecosystem, and a proper volumes API in docker. With plugins your volume can either live locally or on some other storage management system, like ceph, gluster, s3, etc. These are all working solutions today. `docker run -v importatndata:/var/lib/mydata --volume-driver ceph` Run that on two hosts and you get the same data. In 1.9 there is the volume API that allows you to wire this up prior to docker run `docker volume create --driver ceph --o foo=bar --name importantdata`, then `docker run -v importantdata:/var/lib/mydata`
- dpeterson 11y agoGreat, now have someone at Docker package that up in a Docker-Compose, Docker Swarm, Docker Machine template that starts up a Mongodb Replica set and I am happy as a clam.