Hacker News new | ask | show | jobs
by jimbokun 2330 days ago
"It would help with automatically spinning up new replicas when a few nodes go down, changing the number of replicas on the fly, etc."

I'm saying for small deployments even this isn't really needed. If one container dies, have monitoring to alert you and then spin up a new one manually when you get around to it. Obviously, your system needs to have enough redundancy with each kind of container that you can still handle the load after losing one.

It's only if you are changing the number of containers a lot that something like Kubernetes is needed. And I think at that point go straight to Kubernetes, I don't know if there is a scenario where adopting Swarm but not full blown Kubernetes is the right answer, because then you likely have to migrate twice. Once to Swarm, and then to Kubernetes.