3 ms·

I certainly hope so - Swarm is a wonderful orchestration system for small deployments (at least, I haven't tried to use it for large ones), and is really easy t

I certainly hope so - Swarm is a wonderful orchestration system for small deployments (at least, I haven't tried to use it for large ones), and is really easy to use. It's also vastly simpler to comprehend and operate that Kubernetes, and doesn't eat CPU & memory for breakfast. I'd wager that Swarm would be a better fit than Kubernetes for most systems.

jswny 7y ago
Totally agree. I tested out both Kubernetes and Swarm for a recent project. Swarm was so vastly easier to not only understand at an architectural level, but to actually use, that I was delighted by using it. Kubernetes, on the other hand, was a real pain, and overly-complicated for 90% of projects I would say. It was even very difficult to setup a test cluster on my MacBook Pro to try out multi-node support (you have to find a good distribution, something that supports Mac for multi-node, etc.). Whereas for Swarm, it was super easy.
rumanator 7y ago
> I certainly hope so - Swarm is a wonderful orchestration system for small deployments (at least, I haven't tried to use it for large ones), and is really easy to use. I would argue that Docker Swarm is a wonderful orchestration system for all practical real-world applications, with the notable exception of really global and gigantic multi-region deployments. Docker Swarm works superbly out of the box and it's trivial to setup a multi-node heterogeneous cluster of COTS hardware and/or VM instances.
- Spivak 7y ago
  I think there's a more specific statement about k8s vs swam. Swam is much better at running other people's applications that you're treating largely as a black box -- k8s excels at running your in-house app. The simpler deployment model means there's far less environment specific weirdness you need to contend to to make an arbitrary app run.
  - GordonS 7y ago
    The systems I've deployed with Swarm have generally been a mix of both - not sure why it would make a difference if you were running in-house or off-the-shelf images?

jswny 7y ago

Totally agree. I tested out both Kubernetes and Swarm for a recent project. Swarm was so vastly easier to not only understand at an architectural level, but to actually use, that I was delighted by using it. Kubernetes, on the other hand, was a real pain, and overly-complicated for 90% of projects I would say. It was even very difficult to setup a test cluster on my MacBook Pro to try out multi-node support (you have to find a good distribution, something that supports Mac for multi-node, etc.). Whereas for Swarm, it was super easy.

rumanator 7y ago

> I certainly hope so - Swarm is a wonderful orchestration system for small deployments (at least, I haven't tried to use it for large ones), and is really easy to use. I would argue that Docker Swarm is a wonderful orchestration system for all practical real-world applications, with the notable exception of really global and gigantic multi-region deployments. Docker Swarm works superbly out of the box and it's trivial to setup a multi-node heterogeneous cluster of COTS hardware and/or VM instances.

Spivak 7y ago
I think there's a more specific statement about k8s vs swam. Swam is much better at running other people's applications that you're treating largely as a black box -- k8s excels at running your in-house app. The simpler deployment model means there's far less environment specific weirdness you need to contend to to make an arbitrary app run.
- GordonS 7y ago
  The systems I've deployed with Swarm have generally been a mix of both - not sure why it would make a difference if you were running in-house or off-the-shelf images?