Apache Mesos vs Yarn

Get Advice Icon

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

Apache Mesos
Apache Mesos

221
243
+ 1
30
Yarn
Yarn

3.8K
2.6K
+ 1
116
Add tool

Apache Mesos vs Yarn: What are the differences?

Apache Mesos: Develop and run resource-efficient distributed systems. Apache Mesos is a cluster manager that simplifies the complexity of running applications on a shared pool of servers; 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.

Apache Mesos belongs to "Cluster Management" category of the tech stack, while Yarn can be primarily classified under "Front End Package Manager".

"Easy scaling" is the primary reason why developers consider Apache Mesos over the competitors, whereas "Incredibly fast" was stated as the key factor in picking Yarn.

Yarn is an open source tool with 36.1K GitHub stars and 2.21K GitHub forks. Here's a link to Yarn's open source repository on GitHub.

According to the StackShare community, Yarn has a broader approval, being mentioned in 609 company stacks & 507 developers stacks; compared to Apache Mesos, which is listed in 61 company stacks and 19 developer stacks.

- No public GitHub repository available -

What is Apache Mesos?

Apache Mesos is a cluster manager that simplifies the complexity of running applications on a shared pool of servers.

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

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

Why do developers choose Apache Mesos?
Why do developers choose Yarn?

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

What companies use Apache Mesos?
What companies use Yarn?

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

What tools integrate with Apache Mesos?
What tools integrate with Yarn?

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

What are some alternatives to Apache Mesos and Yarn?
Mesosphere
Mesosphere offers a layer of software that organizes your machines, VMs, and cloud instances and lets applications draw from a single pool of intelligently- and dynamically-allocated resources, increasing efficiency and reducing operational complexity.
OpenStack
OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter, all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface.
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.
See all alternatives
Decisions about Apache Mesos and Yarn
Tim Abbott
Tim Abbott
Founder at Zulip · | 3 upvotes · 10.3K views
atZulipZulip
Yarn
Yarn
npm
npm
Node.js
Node.js

I have mixed feelings on the Yarn/npm/Node.js ecosystem. We use it for Zulip, because you basically have to in order to have a modern JavaScript toolchain. And I like that Yarn lets us pin dependency versions out of the box for predictability in our production releases; we have to do significant work for the Python version of this feature.

But one also deals with broken third-party dependencies uploaded to npm way too often (even ignoring the malicious packages issues that have gotten a lot of press of late). And one mostly has to use nvm in order to pin a specific version of node itself in a maintainable way, and nvm is a mess.

See more
Russel Werner
Russel Werner
Lead Engineer at StackShare · | 5 upvotes · 7.5K views
atStackShareStackShare
Yarn
Yarn
npm
npm

We use Yarn because at the time we decided to adopt it, npm had some missing features and issues. We like the speed and determinism provided by Yarn. We could probably use npm at this point, but we have no real reason to switch from Yarn. If you have a convincing argument to switch from npm to Yarn please leave a comment on this decision!

See more
Johnny Bell
Johnny Bell
Senior Software Engineer at StackShare · | 17 upvotes · 141.6K views
Webpack
Webpack
Node.js
Node.js
Yarn
Yarn
npm
npm
Babel
Babel
Prettier
Prettier
ESLint
ESLint
#ES6
#ES5

So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

See more
Yarn
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
Mark Nelissen
CTO at Gemsotec bvba · | 4 upvotes · 2.9K views
React
React
TypeScript
TypeScript
Yarn
Yarn
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
Jason Barry
Jason Barry
Cofounder at FeaturePeek · | 4 upvotes · 12.2K views
atFeaturePeekFeaturePeek
Flow (JS)
Flow (JS)
TypeScript
TypeScript
React
React
JavaScript
JavaScript
Sublime Text
Sublime Text
Babel
Babel
Yarn
Yarn
npm
npm
#Frontend

I think our #Frontend stack is pretty standard – but we have taken some deviations from a typical modern stack:

  • Flow (JS) instead of TypeScript. Flow was an easy choice 2+ years ago, as both flow and React were (and still are) maintained by Facebook. Today, it seems that the JavaScript community has settled on TypeScript as the winner. For new projects, I'd choose TS, but I don't see the point in migrating an existing project from flowtype to TS, when the end result will be roughly the same. Sure, memory usage is a bit high, and every now and then I have to kill some zombie processes, but our text editors (Sublime Text), CI scripts, and Babel are already set up to take advantage of the type safety that flow offers. When/if the React team writes React itself in TS, then I'll take a closer look – until then, flow works for us.

  • Yarn instead of npm. When yarn debuted, we never looked back. Now npm has pretty much caught up with speed and lockfiles, but yarn gives me confidence that my dependency installs are deterministic. Really interested in the plug-n-play (PnP) feature that removes the need for a node_modules folder, but haven't implemented this yet.

See more
Node.js
Node.js
npm
npm
Yarn
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
Interest over time
Reviews of Apache Mesos and Yarn
No reviews found
How developers use Apache Mesos and Yarn
Avatar of Ralic Lo
Ralic Lo uses Apache MesosApache Mesos

Built Mesos master/slave as a cluster among serveral cloud service providers, such as Amazon web services, Google cloud engine, Joyent Elastic Container, and AliCloud, and also personal desktop.

Avatar of Mick Dekkers
Mick Dekkers uses YarnYarn

Yarn is a wonderful alternative to the built-in npm command-line interface. Dependency installation is crazy fast, because it caches every package and performs operations in parallel.

Avatar of Volkan Özçelik
Volkan Özçelik uses YarnYarn

I prefer yarn instead of npm.

Both npm and yarn work great.

I don’t see any overwhelming reason to choose one over another.

I just like yarn, that’s it.

Avatar of Ambar
Ambar uses YarnYarn

We use it in every JS project. Blazing fast package manager for node.js. Easy to use in Docker containers

Avatar of Coolfront Technologies
Coolfront Technologies uses YarnYarn

Used in Coolfront Mobile and "Charlie" (flat rate search engine) as packaging mechanism.

Avatar of IVS
IVS uses YarnYarn

We tend to stick to npm, yarn is only a fancy alternative, not 10x better.

Avatar of Robert Hao
Robert Hao uses Apache MesosApache Mesos

Bamboo + Marathon + Mesos (+ Docker) => awesome tool set to building PaaS.

Avatar of BrainFinance
BrainFinance uses Apache MesosApache Mesos

As a part of big data machine learning stack (SMACK).

How much does Apache Mesos cost?
How much does Yarn cost?
Pricing unavailable
Pricing unavailable