CODEWITHSUNDEEP
node.jsmeteor
ronih
ronih

Reputation: 41

Node.JS/Meteor on multiple servers serving the same application

When coming to deploy Node.JS/Meteor for large scale application a single CPU will not be sufficient. We also would like to have it on multiple servers for redundancy.

What is the recommended setup for such deployment ? how does the load balancing works ? will this support the push data technology for cross servers clients (one client connects to server 1, 2nd client connects to server 2 and we would like an update in client one to be seen in client 2 and vice versa).

Thanks Roni.

Upvotes: 3

Views: 1203

Answers (2)

Michael Bironneau
Michael Bironneau

Reputation: 1

An alternative solution is to use Hipache to manage the load balancing. You can use multiple workers (backends) for one frontent, like so:

$ redis-cli rpush frontend:www.yourdomain.com http://address.of.server.2
$ redis-cli rpush frontend:www.yourdomain.com http://address.of.server.2

There is more information on how to do this in the git page I linked to above, there is a single config file to edit and the rest is done for you. You may also want to have a dedicated server for MongoDB.

Upvotes: 0

Tarang
Tarang

Reputation: 75945

At the moment you just need to use a proxy between them. The paid galaxy solution should help but details are scarce at the moment as the product isn't out yet.

You can't simply proxy (normally using nginx, etc) between two servers as each server will store the user's state (i.e their login state) during the DDP Session (the raw wire protocol meteor uses to transmit data).

There is one way you could do it at the moment. Get meteorite and install a package called meteor-cluster.

The package should help you relay data between instances and relay data between the instances via Redis. A youtube video also shows this and how to set it up.

Upvotes: 1

Related Questions