Created
May 4, 2014 20:45
-
-
Save sebyx07/9e9a174377306b3654c4 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is the scheme of the ap | |
 | |
* * * | |
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](https://github.com/phusion/passenger/wiki/Phusion-Passenger:-Meteor-tutorial) 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