Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Docker Swarm
Docker Swarm

427
412
+ 1
207
Weave
Weave

36
31
+ 1
7
Add tool

Docker Swarm vs Weave: What are the differences?

Developers describe Docker Swarm as "Native clustering for Docker. Turn a pool of Docker hosts into a single, virtual host". Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself. On the other hand, Weave is detailed as "Weave creates a virtual network that connects Docker containers deployed across multiple hosts". Weave can traverse firewalls and operate in partially connected networks. Traffic can be encrypted, allowing hosts to be connected across an untrusted network. With weave you can easily construct applications consisting of multiple containers, running anywhere.

Docker Swarm and Weave can be primarily classified as "Container" tools.

"Docker friendly" is the top reason why over 44 developers like Docker Swarm, while over 2 developers mention "Easy setup" as the leading cause for choosing Weave.

Docker Swarm and Weave are both open source tools. Docker Swarm with 5.63K GitHub stars and 1.11K forks on GitHub appears to be more popular than Weave with 5.57K GitHub stars and 517 GitHub forks.

Docker, Bugsnag, and Dial Once are some of the popular companies that use Docker Swarm, whereas Weave is used by Excursiopedia, Tutum, and PlanetPass. Docker Swarm has a broader approval, being mentioned in 82 company stacks & 38 developers stacks; compared to Weave, which is listed in 11 company stacks and 4 developer stacks.

What is Docker Swarm?

Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself.

What is Weave?

Weave can traverse firewalls and operate in partially connected networks. Traffic can be encrypted, allowing hosts to be connected across an untrusted network. With weave you can easily construct applications consisting of multiple containers, running anywhere.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Docker Swarm?
Why do developers choose Weave?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    Jobs that mention Docker Swarm and Weave as a desired skillset
    What companies use Docker Swarm?
    What companies use Weave?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Docker Swarm?
    What tools integrate with Weave?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Docker Swarm and Weave?
    Docker Compose
    With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.
    Rancher
    Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform.
    Ansible
    Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible鈥檚 goals are foremost those of simplicity and maximum ease of use.
    Apache Mesos
    Apache Mesos is a cluster manager that simplifies the complexity of running applications on a shared pool of servers.
    Kubernetes
    Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
    See all alternatives
    Decisions about Docker Swarm and Weave
    Yshay Yaacobi
    Yshay Yaacobi
    Software Engineer | 27 upvotes 271.2K views
    atSolutoSoluto
    Docker Swarm
    Docker Swarm
    Kubernetes
    Kubernetes
    Visual Studio Code
    Visual Studio Code
    Go
    Go
    TypeScript
    TypeScript
    JavaScript
    JavaScript
    C#
    C#
    F#
    F#
    .NET
    .NET

    Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

    Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

    After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

    See more
    Interest over time
    Reviews of Docker Swarm and Weave
    No reviews found
    How developers use Docker Swarm and Weave
    No items found
    How much does Docker Swarm cost?
    How much does Weave cost?
    Pricing unavailable
    Pricing unavailable