Why Databases Are Not for Docker Containers
I still can't really figure out what a container is. Every time I think of a use case for one, I read something like this which says that's a terrible idea.<p>The use-case I need solved most often is the following:<p>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. Do I just want a bunch of VMs? Or docker instances that all point to some other DB (that's apparently not in a docker instance...?). But then they're no longer independent from one another because they all use the same DB. So do I need a separate DB for each serverlet? Which lives where? On its own VM?