4 ms·

Out of curiosity, how do you deploy new versions of your without downtime (start new containers, wait for new containers to be ready, switch traffic to new cont

• giobox 8y ago
  For me personally zero downtime upgrades are a little beyond the scope of "personal project" and veering into something more production quality. If I really had to for one of these, I'd probably just do something at the loadbalancer to start routing users to the new container stack then shutdown the old ones, much as you might have in the pre-container days. I can just wait the old fashioned way (by sitting in my chair for a minute) for them to start.
  • ngrilly 8y ago
    Ok, this is basically what I do with an Ansible script, but I see it as a bit messy and non-standard, which is why I'm attracted to Docker swarm mode and Kubernetes (and maybe Nomad).
    • giobox 8y ago
      Fair, but I think it's arguable there isn't really a "standard" way for container orchestration, and Docker Swarm to me is starting to feel like a dead horse, despite protestations to the contrary from Docker. The requirements of different software always make each project's needs for zero downtime upgrades different enough, especially if you are dealing with legacy software. Pick the one that works best for you and your projects goals (within reason...).
      • ngrilly 8y ago
        Right, there isn't really a "standard". There are so much existing solutions: Kubernetes, Docker swarm mode, Nomad, Spinnaker, etc. What I meant by "standard" is something used by more than one team :-) Agreed by Docker swarm mode feeling a bit abandoned. Do you have any recommendation for a solution that I would have missed?