cluster

Clustering solution for Meteor with load balancing and service discovery

Networking

Explore on GitHub Read Hacker News discussions

3Distinct people

3Mentions

0Explicit recommenders

622GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Clustering solution for Meteor with load balancing and service discovery

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month3 dated mentions

Observed mentions: 2015-10-15 21:45:15 UTC to 2016-10-17 00:03:04 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
Oct 2015	2015-10-01 00:00:00 UTC	2015-11-01 00:00:00 UTC	1	1
Nov 2015	2015-11-01 00:00:00 UTC	2015-12-01 00:00:00 UTC	0	0
Dec 2015	2015-12-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	0	0
Jan 2016	2016-01-01 00:00:00 UTC	2016-02-01 00:00:00 UTC	1	1
Feb 2016	2016-02-01 00:00:00 UTC	2016-03-01 00:00:00 UTC	0	0
Mar 2016	2016-03-01 00:00:00 UTC	2016-04-01 00:00:00 UTC	0	0
Apr 2016	2016-04-01 00:00:00 UTC	2016-05-01 00:00:00 UTC	0	0
May 2016	2016-05-01 00:00:00 UTC	2016-06-01 00:00:00 UTC	0	0
Jun 2016	2016-06-01 00:00:00 UTC	2016-07-01 00:00:00 UTC	0	0
Jul 2016	2016-07-01 00:00:00 UTC	2016-08-01 00:00:00 UTC	0	0
Aug 2016	2016-08-01 00:00:00 UTC	2016-09-01 00:00:00 UTC	0	0
Sep 2016	2016-09-01 00:00:00 UTC	2016-10-01 00:00:00 UTC	0	0
Oct 2016	2016-10-01 00:00:00 UTC	2016-11-01 00:00:00 UTC	1	1

What Hacker News says

3 sources

asenna·Oct 17, 2016

+1 for Meteor. I'm pretty sure Jason uses Mupx for deployment to DigitalOcean (https://github.com/arunoda/meteor-up/tree/mupx). For anyone interested, this package makes it super easy to setup all the tools and deploy to the servers (almost as easy as pushing to Heroku!). I've had good experience in scaling using Mupx and Cluster (another package from the same team - https://github.com/meteorhacks/cluster)

In SubmitHub: how a solo founder built a $46k/mo SaaS business in 10 months

vskarine·Jan 21, 2016

Most meteor apps are stateless on the server so you can safely scale by adding more servers (and more server to Mongo if that's the bottleneck). This can be easily done with Cluster package (https://github.com/meteorhacks/cluster). It's so easy you don't even need to configure anything.

In The State of Meteor Part 2: What Happens Next

n17r4m·Oct 15, 2015

IMHO, its been getting progressively better as time goes on. It has great support for React and Angular now, in addition to its own Blaze templating engine (I prefer Blaze, actually). The data sync is fast enough to be useful for real-time games. When it comes time to scale up, ditch the built-in mongo (or sql) and set up your DB cluster, and for the web bits, use something like https://github.com/meteorhacks/cluster and you are off to the horizontal scaling races. In response to the linked posts criticism: No API-based authentication: having a REST api to interface with Accounts is not there by default, but Meteor does support adding REST endpoints, where one could easily roll a solution that does a server-side auth and respond with an auth token which could be stored in the user's record as appropriate. I'd be surprised if there wasn't

Read the rest

already a package available which does exactly this. App shutdown: Once you are running a 'real' site, you will probably have a separate mongo instance. This solves most of the problems, however yes, it is still possible for some 'in-flight' data to be lost. Adding a maintenance mode like https://github.com/yogiben/meteor-maintenance-mode solves this though. Subscriptions scalability: It's all about writing publish functions that only send what you need for a particular screen / template / page. In practice, it is not difficult and can scale up quite nicely: http://meteor.redandivory.com/ Server-side rendering for SEO: As the link points out, there are community packages that can make this happen. The beauty of meteor is the huge amount of community packages available that are almost universally of high quality. Their use should be encouraged, and is not considered "hacky". My 2c.

In Ask HN: Is Meteor.js production-ready now?