Apache Mesos vs Webpack

Overview

Apache Mesos

Stacks306

Followers418

Votes31

GitHub Stars5.3K

Forks1.7K

Webpack

Stacks45.0K

Followers28.1K

Votes752

GitHub Stars65.7K

Forks9.2K

Apache Mesos vs Webpack: What are the differences?

Developers describe Apache Mesos as "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. On the other hand, Webpack is detailed as "A bundler for javascript and friends". A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.

Apache Mesos and Webpack are primarily classified as "Cluster Management" and "JS Build Tools / JS Task Runners" tools respectively.

"Easy scaling" is the primary reason why developers consider Apache Mesos over the competitors, whereas "Most powerful bundler" was stated as the key factor in picking Webpack.

Webpack is an open source tool with 49.8K GitHub stars and 6.27K GitHub forks. Here's a link to Webpack's open source repository on GitHub.

Airbnb, Instagram, and Pinterest are some of the popular companies that use Webpack, whereas Apache Mesos is used by Airbnb, Netflix, and Twitter. Webpack has a broader approval, being mentioned in 2207 company stacks & 1339 developers stacks; compared to Apache Mesos, which is listed in 61 company stacks and 19 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Apache Mesos, Webpack

Aleksandr

Contract Software Engineer - Microsoft at Microsoft-365

Dec 23, 2019

Decided

Why migrated?

I could define the next points why we have to migrate:

Decrease build time of our application. (It was the main cause).
Also jspm install takes much more time than npm install.
Many config files for SystemJS and JSPM. For Webpack you can use just one main config file, and you can use some separate config files for specific builds using inheritance and merge them.

301k views301k

Comments

Abigail

Dec 10, 2019

Decided

We mostly use rollup to publish package onto NPM. For most all other use cases, we use the Meteor build tool (probably 99% of the time) for publishing packages. If you're using Node on FHIR you probably won't need to know rollup, unless you are somehow working on helping us publish front end user interface components using FHIR. That being said, we have been migrating away from Atmosphere package manager towards NPM. As we continue to migrate away, we may publish other NPM packages using rollup.

224k views224k

Comments

Detailed Comparison

Apache Mesos	Webpack
Apache Mesos is a cluster manager that simplifies the complexity of running applications on a shared pool of servers.	A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
Fault-tolerant replicated master using ZooKeeper;Scalability to 10,000s of nodes;Isolation between tasks with Linux Containers;Multi-resource scheduling (memory and CPU aware);Java, Python and C++ APIs for developing new parallel applications;Web UI for viewing cluster state	Bundles ES Modules, CommonJS, and AMD modules (even combined); Can create a single bundle or multiple chunks that are asynchronously loaded at runtime (to reduce initial loading time); Dependencies are resolved during compilation, reducing the runtime size; Loaders can preprocess files while compiling, e.g. TypeScript to JavaScript, Handlebars strings to compiled functions, images to Base64, etc; Highly modular plugin system to do whatever else your application requires
Statistics
GitHub Stars 5.3K	GitHub Stars 65.7K
GitHub Forks 1.7K	GitHub Forks 9.2K
Stacks 306	Stacks 45.0K
Followers 418	Followers 28.1K
Votes 31	Votes 752
Pros & Cons
Pros 21 Easy scaling 6 Web UI 2 Fault-Tolerant 1 Elastic Distributed System 1 High-Available Cons 1 Not for long term 1 Depends on Zookeeper	Pros 309 Most powerful bundler 182 Built-in dev server with livereload 142 Can handle all types of assets 87 Easy configuration 22 Laravel-mix Cons 15 Hard to configure 5 No clear direction 2 Fire and Forget mentality of Core-Developers 2 SystemJS integration is quite lackluster 2 Spaghetti-Code out of the box
Integrations
Apache Aurora	JavaScript

What are some alternatives to Apache Mesos, Webpack?

gulp

Build system automating tasks: minification and copying of all JavaScript files, static images. More capable of watching files to automatically rerun the task when a file changes.

Grunt

The less work you have to do when performing repetitive tasks like minification, compilation, unit testing, linting, etc, the easier your job becomes. After you've configured it, a task runner can do most of that mundane work for you—and your team—with basically zero effort.

Brunch

Brunch is an assembler for HTML5 applications. It's agnostic to frameworks, libraries, programming, stylesheet & templating languages and backend technology.

Nomad

Nomad is a cluster manager, designed for both long lived services and short lived batch processing workloads. Developers use a declarative job specification to submit work, and Nomad ensures constraints are satisfied and resource utilization is optimized by efficient task packing. Nomad supports all major operating systems and virtualized, containerized, or standalone applications.

Parcel

Parcel is a web application bundler, differentiated by its developer experience. It offers blazing fast performance utilizing multicore processing, and requires zero configuration.

rollup

It is a module bundler for JavaScript which compiles small pieces of code into something larger and more complex, such as a library or application. It uses the new standardized format for code modules included in the ES6 revision of JavaScript, instead of previous idiosyncratic solutions such as CommonJS and AMD.

Backpack

Backpack is minimalistic build system for Node.js. Inspired by Facebook's create-react-app, Zeit's Next.js, and Remy's Nodemon, Backpack lets you create modern Node.js apps and services with zero configuration. Backpack handles all the file-watching, live-reloading, transpiling, and bundling, so you don't have to.

Vite

It is an opinionated web dev build tool that serves your code via native ES Module imports during dev and bundles it with Rollup for production.

DC/OS

Unlike traditional operating systems, DC/OS spans multiple machines within a network, aggregating their resources to maximize utilization by distributed applications.

Pingy CLI

Gulp and Grunt and other heavyweight build tools are great for complicated build workflows. Sometimes you want something simpler that doesn't take lots of configuration to get up and running. That's Pingy CLI.

Related Comparisons

Bitbucket vs GitHub vs GitLab

AWS CodeCommit vs Bitbucket vs GitHub

Docker Swarm vs Kubernetes vs Rancher

Grunt vs Webpack vs gulp

Grafana vs Graphite vs Kibana

Apache Mesos vs Webpack: What are the differences?

Apache Mesos and Webpack are primarily classified as "Cluster Management" and "JS Build Tools / JS Task Runners" tools respectively.

"Easy scaling" is the primary reason why developers consider Apache Mesos over the competitors, whereas "Most powerful bundler" was stated as the key factor in picking Webpack.

Webpack is an open source tool with 49.8K GitHub stars and 6.27K GitHub forks. Here's a link to Webpack's open source repository on GitHub.