Docker orchestration refers to container orchestration, which refers to the process of organizing the work of individual components and application layers; all container orchestration engines allow users to control the time when containers start and stop, and The process of grouping groups into clusters and coordinating application groups.
The operating environment of this article: ubuntu 18.04 system, Docker version 20.10.11, Dell G3 computer.
What does docker orchestration mean?
Container orchestration:
Applications generally consist of individually containerized components (often called Microservices) and must be organized sequentially at the network level to enable them to run according to plan. The process of organizing multiple containers in this way is called container orchestration.
Container orchestration definition:
In modern development, monolithic applications have long become a thing of the past. Today’s applications range from dozens to even tens of thousands. It is composed of hundreds of loosely combined container components, and these components need to cooperate with each other to make the given application operate as designed. Container orchestration refers to the process of organizing the work of individual components and application layers.
How container orchestration works:
Although platforms such as Apache Mesos, Google Kubernetes and Docker Swarm have their own specific container management methods , but all container orchestration engines allow users to control when containers are started and stopped, grouped into clusters, and orchestrate the process of application composition. Container orchestration tools allow users to guide the steps of container deployment and automatic updates, health monitoring, and failover.
Docker swarm mode
If you are a new container user, you can start with Docker, which is the first container to attract a large number of users program. If you are using Docker, then Docker swarm is a natural choice, it is designed and developed by Docker developers.
In version 1.12 of Docker, Docker’s goal is to have a built-in container orchestration function called docker swarm mode. Docker Swarm, a separate orchestrator within the Docker software stack, has impacted this built-in orchestrator. Swarm mode allows users to control the entire life cycle of the container, not just container cluster management and scheduling.
What is the difference between Docker Swarm and Swarm mode? In Docker 1.12, Swarm mode has become part of Docker Engine. Scaling, container discovery, and security are all included in the minimal setup. Docker Swarm is an older standalone product that was once used to manage Docker clusters. Swarm mode is Docker's built-in cluster manager.
Swarm mode uses the concept of a single node and can be expanded into a Swarm cluster. Switch to swarm mode through the docker swarm init command and add more nodes through docker swarm join.
In addition, Docker 1.12 and higher and swarm mode support rolling updates, inter-node transport layer security encryption, load balancing and simple service abstraction.
In short, Docker swarm mode can spread container load among multiple hosts, which allows you to set up swarm (i.e. cluster) on multiple host platforms. This also requires simple configuration on your host platform, including integration (so that containers can communicate across multiple hosts) and isolation (isolating and protecting different container workloads). You may also need a virtual network to meet your needs.
Recommended learning: "Docker Video Tutorial"
The above is the detailed content of What does docker orchestration mean?. For more information, please follow other related articles on the PHP Chinese website!