Why Databases Are Not for Docker Containers
I still can&#x27;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&#x27;s a terrible idea.<p>The use-case I need solved most often is the following:<p>Create a standalone &quot;server&quot; 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 &quot;servers&quot; I have running. Do I just want a bunch of VMs? Or docker instances that all point to some other DB (that&#x27;s apparently not in a docker instance...?). But then they&#x27;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?