5 ms·
I have written a 1mm+ simultaneous user websocket server for a second screen app for a well known talent TV show in Node. It was running on a single server (wit
by art0rz 8y ago
I have written a 1mm+ simultaneous user websocket server for a second screen app for a well known talent TV show in Node. It was running on a single server (with failovers and redundancies of course) just fine, but 99% of the server was just broadcasting. The hard part is sending single messages to users with user-specific content.
- toredash 8y agoAgree on the hard part. Fan out models like this with the same content is "easy". Getting unique content to specific users in an efficient way, in scale of 100.000 users plus, that's hard.
- zepolen 8y agoDo you have an example of this type of unique content?
- toredash 8y agoQuiz for instance with a leaderboard or prizing. Let say you publish an Quiz to 1 mill users. Everyone response and you store the responses centrally. Now you send out an aggregated view of the results (e.g. % answered A). Now, you want to inform one or more users that they won a prize. How do you do this effectively ? Of better, you want to display the ranking to each user if there are multiple quiz.