Deployment with Docker

Rolling service restarts

If the new service code does not change the fundamental way that it interacts with other services (inputs and outputs), often the only thing that is needed is a rebuild (or replacement) of the container image that is then placed into the Docker registry, and then the service is restarted in an orderly and staggered way. By staggering the restarts, there is always at least one task that can handle the service request available, and from an external point of view, this changeover should be completely seamless. Most orchestration tooling will do this automatically for you if you change or update any settings for a service, but since they are very implementation-specific we will focus on Docker Swarm for our examples: ...