> docker containers are not meant to be persistent. Things like storage and state should be kept elsewhere and linked into your containers. This just means you

> docker containers are not meant to be persistent. Things like storage and state should be kept elsewhere and linked into your containers. This just means you need two systems to handle job creation, migration, replication, and load balancing. Everything you listed for docker containers is also needed for databases. You need to remember: At scale, nothing is persistent. You need to notice a failure in your database systems,tear down the broken one, spin up a new instance, migrate the data from a replica, and keep on going.