Skip to content

Instantly share code, notes, and snippets.

@sebyx07

sebyx07/gist:508384d493f4b5d58ef9

Created May 4, 2014 20:45
Show Gist options
  • Save sebyx07/508384d493f4b5d58ef9 to your computer and use it in GitHub Desktop.
Save sebyx07/508384d493f4b5d58ef9 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
gistfile1.md

This is the scheme of the ap

Imgur

i use the node.js server for a match-making thing, a queue of users.

  1. meteor sends users(players) to the node server .

  2. node stores the users and creates parties of players

  3. send the parties created back to meteor

My question is, does it matter which meteor instance recives the party such that there is no duplication ?

Or i should save the party to the database, but i need confirmation from the users. so it will generate useless data too.

Also how i can connect the node and the meteor with pub/sub

I want to use streams for something like chatting, user status etc, will users recive duplicate data ?

As for load balancing i've seen phussion passenger and also it spawns new instances of meteor. Is this working with meteor cluster ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment