4 ms·
Not to hijack the thread, just wondering anyone has experience with zero-downtime deployment of multi-container app with cross-container communication?
by jlu 11y ago
Not to hijack the thread, just wondering anyone has experience with zero-downtime deployment of multi-container app with cross-container communication?
- pantulis 11y agoI think this is the golden question regarding this stuff... would love to have any blog post about this.
- InTheArena 11y agoChallange accepted - I'll put together something this weekend. What are you exactly looking for?
- InTheArena 11y agoI would definitely check out a number of docker related technologies. To answer your question, we don't have our software out in Docker yet, but it's coming, and it will make a splash when it lands. Vagrant is a great technology, but I recommend taking a look at Docker compose (https://docs.docker.com/compose/ https://docs.docker.com/compose/) previously known as FIG. One of the great advantages of compose is that combine it with Swarm (https://github.com/docker/swarm https://github.com/docker/swarm) and you have a very robust distributed deployment system. Docker-machine is the direct competitor to vagrant, but to be honest, I don't use it. I spin up my docker containers via some build in service API's we already built for proprietary reasons. If you want to get really robust, you can also look at Kubernetes (and their zero-downtime deployment) and Mesos. These both add a huge amount of complexity t the deployment, but also grant a robust distributed system for managing downtime and deployment. Redhat also has Openshift.
- jlu 11y agoYep, machine/compose/swarm are great tools from Docker and I'm already using it, but compose is more of a "dev" tool so it restarts all containers with every new deploy. What I'm looking for is a robust and systematic zero-downtime approach to update some of the containers (say in a loadBalancer → web servers → db architecture).