Home Operation and Maintenance Docker Reasons why the database is not suitable for docker and containerization

Reasons why the database is not suitable for docker and containerization

Apr 15, 2020 am 10:01 AM
docker Containerization database

Reasons why the database is not suitable for docker and containerization

There are several reasons why the database is not suitable for docker and containerization:

1. Data is not safe

Even if you want to put Docker data on the host To store, it still cannot guarantee that data will not be lost. Docker volumes are designed around the Union FS image layer to provide persistent storage, but it still lacks guarantees.

With the current storage driver, Docker is still at risk of being unreliable. If the container crashes and the database is not shut down properly, data may be corrupted.

2. Environmental requirements for running the database

It is common to see DBMS containers and other services running on the same host. However, the hardware requirements for these services are very different.

Databases (especially relational databases) have higher IO requirements. Typically database engines use dedicated environments to avoid contention for concurrent resources. If you put your database in a container, you will waste your project's resources. Because you need to configure a lot of additional resources for this instance. In the public cloud, when you need 34G of memory, the instance you start must have 64G of memory. In practice, these resources are not fully used.

How to deal with it? You can design in layers and use fixed resources to launch multiple instances at different tiers. Scaling horizontally is always better than scaling vertically.

3. Network issues

To understand the Docker network, you must have an in-depth understanding of network virtualization. You must also be prepared to deal with the unexpected. You may need to perform bug fixes without support or additional tools.

4. State

It’s cool to package stateless services in Docker, which can orchestrate containers and solve single points of failure. But what about the database? By placing the database in the same environment, it will be stateful and make the scope for system failure greater. The next time your application instance or application crashes, it may affect the database.

5. Additional isolation is detrimental to the database

In fact, I mentioned this in the second and third reasons. But I list this as a separate reason because I want to emphasize this fact again. The more isolation levels we have, the more resource overhead we get. Easily scaling horizontally allows us to gain more benefits than a dedicated environment. However, horizontal scaling in Docker can only be used for stateless computing services, not databases.

We don’t see any isolation functionality for the database, so why should we put it in a container?

Recommended tutorial: docker tutorial

The above is the detailed content of Reasons why the database is not suitable for docker and containerization. For more information, please follow other related articles on the PHP Chinese website!

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

How to update the image of docker How to update the image of docker Apr 15, 2025 pm 12:03 PM

The steps to update a Docker image are as follows: Pull the latest image tag New image Delete the old image for a specific tag (optional) Restart the container (if needed)

How to use docker desktop How to use docker desktop Apr 15, 2025 am 11:45 AM

How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

How to exit the container by docker How to exit the container by docker Apr 15, 2025 pm 12:15 PM

Four ways to exit Docker container: Use Ctrl D in the container terminal Enter exit command in the container terminal Use docker stop <container_name> Command Use docker kill <container_name> command in the host terminal (force exit)

How to copy files in docker to outside How to copy files in docker to outside Apr 15, 2025 pm 12:12 PM

Methods for copying files to external hosts in Docker: Use the docker cp command: Execute docker cp [Options] <Container Path> <Host Path>. Using data volumes: Create a directory on the host, and use the -v parameter to mount the directory into the container when creating the container to achieve bidirectional file synchronization.

How to check the name of the docker container How to check the name of the docker container Apr 15, 2025 pm 12:21 PM

You can query the Docker container name by following the steps: List all containers (docker ps). Filter the container list (using the grep command). Gets the container name (located in the "NAMES" column).

How to create a mirror in docker How to create a mirror in docker Apr 15, 2025 am 11:27 AM

Steps to create a Docker image: Write a Dockerfile that contains the build instructions. Build the image in the terminal, using the docker build command. Tag the image and assign names and tags using the docker tag command.

How to save docker image How to save docker image Apr 15, 2025 am 11:54 AM

To save the image in Docker, you can use the docker commit command to create a new image, containing the current state of the specified container, syntax: docker commit [Options] Container ID Image name. To save the image to the repository, you can use the docker push command, syntax: docker push image name [: tag]. To import saved images, you can use the docker pull command, syntax: docker pull image name [: tag].

What to do if the docker image fails What to do if the docker image fails Apr 15, 2025 am 11:21 AM

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

See all articles