Get Advice Icon

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

Compose
Compose

182
95
+ 1
205
Docker Swarm
Docker Swarm

428
413
+ 1
207
Add tool

Compose vs Docker Swarm: What are the differences?

Compose: We host databases for busy devs: production-ready, cloud-hosted, open source. Compose makes it easy to spin up multiple open source databases with just one click. Deploy MongoDB for production, take Redis out for a performance test drive, or spin up RethinkDB in development before rolling it out to production; Docker Swarm: 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.

Compose can be classified as a tool in the "MongoDB Hosting" category, while Docker Swarm is grouped under "Container Tools".

"Simple to set up" is the top reason why over 41 developers like Compose, while over 44 developers mention "Docker friendly" as the leading cause for choosing Docker Swarm.

Docker Swarm is an open source tool with 5.63K GitHub stars and 1.11K GitHub forks. Here's a link to Docker Swarm's open source repository on GitHub.

Docker, Bugsnag, and Hammerhead are some of the popular companies that use Docker Swarm, whereas Compose is used by Accenture, Artsy, and FashionUnited. Docker Swarm has a broader approval, being mentioned in 83 company stacks & 38 developers stacks; compared to Compose, which is listed in 82 company stacks and 19 developer stacks.

- No public GitHub repository available -

What is Compose?

Compose makes it easy to spin up multiple open source databases with just one click. Deploy MongoDB for production, take Redis out for a performance test drive, or spin up RethinkDB in development before rolling it out to production.

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.
Get Advice Icon

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

Why do developers choose Compose?
Why do developers choose Docker Swarm?

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

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

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

    What tools integrate with Compose?
    What tools integrate with Docker Swarm?

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

    What are some alternatives to Compose and Docker Swarm?
    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.
    Docker
    The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere
    Composer
    It is a tool for dependency management in PHP. It allows you to declare the libraries your project depends on and it will manage (install/update) them for you.
    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.
    Elementor
    Create beautiful websites using a simple, intuitive drag and drop Interface.It offers pixel perfect design, yet produces 100% clean code. Take your design vision and turn it into a stunning custom-made website. It's fast and easy.
    See all alternatives
    Decisions about Compose and Docker Swarm
    Gregory Koberger
    Gregory Koberger
    Compose
    Compose
    MongoLab
    MongoLab
    MongoDB Atlas
    MongoDB Atlas
    PostgreSQL
    PostgreSQL
    MySQL
    MySQL
    MongoDB
    MongoDB

    We went with MongoDB , almost by mistake. I had never used it before, but I knew I wanted the *EAN part of the MEAN stack, so why not go all in. I come from a background of SQL (first MySQL , then PostgreSQL ), so I definitely abused Mongo at first... by trying to turn it into something more relational than it should be. But hey, data is supposed to be relational, so there wasn't really any way to get around that.

    There's a lot I love about MongoDB, and a lot I hate. I still don't know if we made the right decision. We've been able to build much quicker, but we also have had some growing pains. We host our databases on MongoDB Atlas , and I can't say enough good things about it. We had tried MongoLab and Compose before it, and with MongoDB Atlas I finally feel like things are in a good place. I don't know if I'd use it for a one-off small project, but for a large product Atlas has given us a ton more control, stability and trust.

    See more
    Yshay Yaacobi
    Yshay Yaacobi
    Software Engineer · | 27 upvotes · 287.6K 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 Compose and Docker Swarm
    No reviews found
    How developers use Compose and Docker Swarm
    Avatar of PSESD
    PSESD uses ComposeCompose

    Hosts primary MongoDB database

    Avatar of GREGORY NICHOLAS
    GREGORY NICHOLAS uses ComposeCompose

    hosts redis, rabbitmq.

    Avatar of Chris Matheson
    Chris Matheson uses ComposeCompose

    data persistence

    How much does Compose cost?
    How much does Docker Swarm cost?
    Pricing unavailable
    News about Compose
    More news