As we've already learned, there are different approaches to persistence in containers. Choosing the right solution will depend on the use case or requirements of the environment and our applications.
Local persistence
We will use local directories or files whenever we are deploying applications on isolated and standalone Docker daemons. In this approach, you should take care of filesystem permissions and secure module configurations. This strategy is quite interesting for developers as they can run multi-container applications on their laptops using local source code files inside containers. Therefore, all changes made on their local files will be synced within the containers (in fact, they will not quite be synced; rather, they are the same files that are mounted inside the container filesystem as a bind mount volume). We will review some examples of this in the Chapter labs section. This solution will not provide high availability...