# Container Orchestration So far we have seen that with Docker we can run a single instance of the application with simple Docker run command. But that just the one instance of our application on one Docker HOST. What happens when the number of users incerases & the instance is no longer able to handle then load . \>>>We need to deploy mutiple Docker instances by running mutiple docker run commands . But that is soemthing that we have to do with ourself . We have to keep a close watch to the load , performance of our application & deploy additional instances with ourself and also we have to keep close watch on the health of our application . And if a container was to fail we should be able to detect & run the docker run command again to deploy a another instance of that application. \>>What about the health of the Docker HOST itself . \>>What if the HOST crashes & is inaccessible . The container hosted on that HOST become inaccessible to . So what we do in order to solve these issues Container Orchestration is the solution . \>>When we have large application deployed with thousand of containers . Container Orchestration is required. \>>Typically a Container Orchestration solution consist of multiple HOST that can host containers that way even if one fails application is still accessible thrpugh the others. \>> A Container Orchestration solution easily allows us to deply hundreds or thousands of instances of our application with a single command . Some orchestration solutions can help us to automatically scale up number of instances when users increase & scale down number of instances when the demand decreases. \>>>Some solutions can even help us in automatically adding additonal HOSTS to support the user load & not just clustering & scaling the container orchetsration solutions also provides the port for advanced networking between these containers across diffrent HOSTS as well LOAD balancing user requests acrosss diffrent HOSTS . They also provide support for sharing stoarge between the HOSTS as well support for Confguration management , security between the clusters. ![](/files/-MEafNguQZobLkMC5mPe) Orhestration solutions: ![](/files/-MEagx7qKSZ6L5JA-lej) \>>>Docker swarm lacks some of the advanced auto-scaling features required for complex production grade applications. \>>MESOS is quite difficult to setup and get started but supoort many advanced features . \>>Kubernetes provides lot of options to customize deployments & has support for many diffrent vendors . Kubernetes is now supported on public Cloud platforms service providers like GCP Azure & AWS --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://architectures.gitbook.io/project/docker/container-orchestration-docker-swarm-and-kubernetes/container-orchestration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.