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

Docker Compose

14.1K
10.3K
+ 1
474
Yarn

13K
8.4K
+ 1
142
Add tool

Docker Compose vs Yarn: What are the differences?

Docker Compose: Define and run multi-container applications with Docker. 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; Yarn: A new package manager for JavaScript. Yarn caches every package it downloads so it never needs to again. It also parallelizes operations to maximize resource utilization so install times are faster than ever.

Docker Compose can be classified as a tool in the "Container Tools" category, while Yarn is grouped under "Front End Package Manager".

"Multi-container descriptor" is the primary reason why developers consider Docker Compose over the competitors, whereas "Incredibly fast" was stated as the key factor in picking Yarn.

Docker Compose and Yarn are both open source tools. Yarn with 36.2K GitHub stars and 2.22K forks on GitHub appears to be more popular than Docker Compose with 16.6K GitHub stars and 2.56K GitHub forks.

According to the StackShare community, Docker Compose has a broader approval, being mentioned in 796 company stacks & 626 developers stacks; compared to Yarn, which is listed in 623 company stacks and 528 developer stacks.

Advice on Docker Compose and Yarn
Needs advice
on
npm
and
Yarn

From a StackShare Community member: “I’m a freelance web developer (I mostly use Node.js) and for future projects I’m debating between npm or Yarn as my default package manager. I’m a minimalist so I hate installing software if I don’t need to- in this case that would be Yarn. For those who made the switch from npm to Yarn, what benefits have you noticed? For those who stuck with npm, are you happy you with it?"

See more
Replies (13)
Julian Sanchez
Lead Developer at Chore Champion · | 8 upvotes · 109.3K views
Recommends
Yarn
at

We use Yarn because it allows us to more simply manage our node_modules. It also simplifies commands and increases speed when installing modules. Our teams module download time was cut in half after switching from NPM to Yarn. We now require all employees to use Yarn (to prevent errors with package-lock.json and yarn.lock).

See more
Recommends
npm

I use npm since new version is pretty fast as well (Yarn may be still faster a bit but the difference isn't huge). No need for other dependency and mainly Yarn sometimes do not work. Sometimes when I want to install project dependencies I got error using Yarn but with npm everything is installed correctly.

See more
Recommends
Yarn

p.s.

I am not sure about the performance of the latest version of npm, whether it is different from my understanding of it below. Because I use npm very rarely when I had the following knowledge.

------⏬

I use Yarn because, first, yarn is the first tool to lock the version. Second, although npm also supports the lock version, when you use npm to lock the version, and then use package-lock.json on other systems, package-lock.json Will be modified. You understand what I mean, when you deploy projects based on Git...

See more
Mark Nelissen
Recommends
npm
npm

I use npm because I also mainly use React and TypeScript. Since several typings (from DefinitelyTyped) depend on the React typings, Yarn tends to mess up which leads to duplicate libraries present (different versions of the same type definition), which hinders the Typescript compiler. Npm always resolves to a single version per transitive dependency. At least that's my experience with both.

See more
Recommends
Yarn

As far as I know Yarn is a super module of NPM. But it still needs npm to run.

Yarn was developed by Facebook's guys to fix some npm issues and performance.

If you use the last version of npm most of this problem does not exist anymore.

You can choose the option which makes you more confortable. I like using yarn because I'm used to it.

In the end the packages will be the same. Just try both and choose the one you feel more confortable. :)

See more
Denys Slipetskyy
Recommends
Yarn
at

I use Yarn because it process my dependencies way faster, predictable deps resolution order, upgrade-interactive is very handy + some Yarn specific features (workspaces, Plug’n’Play alternative installation strategy) ...

See more
tataata
Frontend designer and developer · | 2 upvotes · 97.4K views
Recommends
Yarn

Yarn made it painless for the team to sync on versions of packages that we use on the project <3

See more
Francois Leurent
Recommends
npm
at

We tend to stick to npm, yarn is only a fancy alternative, not 10x better. Using a self -hosted private repository (via sinopia/npm-mirror) make package locking (mostly) pointless.

See more
Izzur Zuhri
Recommends
npm

I use npm because it has a lot of community support and the performance difference with alternative tool is not so significant for me.

See more
Recommends
npm

I use npm because its the official package manager for Node. It's reliability, security and speed has increased over time so the battle is over!

See more
Recommends
Yarn

I am a minimalist too. I once had issues with installing Nuxt.js using NPM so I had to install Yarn but I also found that the Dev experience was much better

See more
Digital All
Recommends
npm

I use npm because its packaged with node installation and handles npm tokens in CI/CD tools for private packages/libraries.

See more
Shuuji TAKAHASHI
Recommends
Yarn

I use Yarn because it outputs nice progress messages with cute emoji and installs packages quickly if the package is cached. Also, Yarn creates yarn.lock file which makes the developer use the consistent environment.

See more
Decisions about Docker Compose and Yarn
Oleksandr Fedotov
Senior Software Engineer at joyn · | 3 upvotes · 121.2K views

As we have to build the application for many different TV platforms we want to split the application logic from the device/platform specific code. Previously we had different repositories and it was very hard to keep the development process when changes were done in multiple repositories, as we had to synchronize code reviews as well as merging and then updating the dependencies of projects. This issues would be even more critical when building the project from scratch what we did at Joyn. Therefor to keep all code in one place, at the same time keeping in separated in different modules we decided to give a try to monorepo. First we tried out lerna which was fine at the beginning, but later along the way we had issues with adding new dependencies which came out of the blue and were not easy to fix. Next round of evolution was yarn workspaces, we are still using it and are pretty happy with dev experience it provides. And one more advantage we got when switched to yarn workspaces that we also switched from npm to yarn what improved the state of the lock file a lot, because with npm package-lock file was updated every time you run npm install, frequent updates of package-lock file were causing very often merge conflicts. So right now we not just having faster dependencies installation time but also no conflicts coming from lock file.

See more
Petr Bambušek
Head of Frontend at Mews · | 2 upvotes · 131K views
Chose
Yarn
over
npm
at
()

This was no real choice - we switched the moment Yarn was available, and never looked back. Yarn is the only reasonable frontend package manager that's actually being developed. They even aim to heal the node_modules madness with v2! Npm is just copying its ideas on top of introducing massive bugs with every change.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Docker Compose
Pros of Yarn
  • 120
    Multi-container descriptor
  • 108
    Fast development environment setup
  • 75
    Easy linking of containers
  • 65
    Simple yaml configuration
  • 58
    Easy setup
  • 15
    Yml or yaml format
  • 11
    Use Standard Docker API
  • 7
    Open source
  • 4
    Go from template to application in minutes
  • 4
    Can choose Discovery Backend
  • 2
    Kubernetes integration
  • 2
    Easy configuration
  • 2
    Scalable
  • 1
    Quick and easy
  • 84
    Incredibly fast
  • 21
    Easy to use
  • 12
    Open Source
  • 10
    Can install any npm package
  • 7
    Works where npm fails
  • 6
    Workspaces
  • 2
    Incomplete to run tasks

Sign up to add or upvote prosMake informed product decisions

Cons of Docker Compose
Cons of Yarn
  • 8
    Tied to single machine
  • 5
    Still very volatile, changing syntax often
  • 15
    Facebook
  • 6
    Sends data to facebook
  • 3
    Should be installed separately
  • 2
    Cannot publish to registry other than npm

Sign up to add or upvote consMake informed product decisions

What is 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.

What is Yarn?

Yarn caches every package it downloads so it never needs to again. It also parallelizes operations to maximize resource utilization so install times are faster than ever.

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

Jobs that mention Docker Compose and Yarn as a desired skillset
What companies use Docker Compose?
What companies use Yarn?
See which teams inside your own company are using Docker Compose or Yarn.
Sign up for Private StackShareLearn More

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

What tools integrate with Docker Compose?
What tools integrate with Yarn?

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

Blog Posts

+29
15
11372
+47
47
69137
+26
19
4598
+42
52
19786
What are some alternatives to Docker Compose and Yarn?
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.
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
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.
Helm
Helm is the best way to find, share, and use software built for Kubernetes.
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’s goals are foremost those of simplicity and maximum ease of use.
See all alternatives