Large database on docker?

Question

Docker

Hello everyone, while I smoke docker, a question arose with real life. How good is the idea to deploy a large high load database inside docker?

Answer 1

Docker is well suited for staitless applications.
And what advantages will remain for the database? It will no longer be possible to take it and run it on another host without data on the disk - portability is lost.
With a high load, volume mounts will also add a bottleneck.
Those. in practice, databases are most often deployed outside the docker / kubernetes cluster. Perhaps someone will name in the answers the advantages of the database in the docker.

Answer 2

Don't use data containers, it's inherently bad practice, debatable even in the rare cases where they are used.
Data containers were used at a time when user volumes had not yet been brought into docker, then the typical way to create one that does not explicitly belong to any "heavy" container was to create a lightweight container that does nothing, from which everyone pulled data to itself.
Now you just do volume and that's it.But for the database there is no point in doing volume, it's easier and more reliable to forward the physical directory.

Answer 3

It's a good idea to do everything in docker. In many ways, it simplifies life during deployment.