Meteor Devshop 2: How Spark Works, Meteor 101, 26Plays, and other wisdom
meteor.com
meteor.com
The leaderboard example (http://meteor.com/examples/leaderboard) works because it is easy to synchronize with a datastore that contains at most a few hundred values. It's so tiny the whole dataset can be kept in the web browsers memory.
Say you have a database with 100k searchable indexed documents. You run the query "foo" to fetch the 10 best matches and also a count of how many documents among the total number of documents searched that matched the query. Now if someone simultaneously adds another document, the whole search query must be run again because the new document might match "foo" and even if it doesn't, the total document count still needs to be updated. Multiply that by a few concurrent clients and performance goes down the drain.
The above scenario or permutations of it is incredibly common in web applications and I don't think Meteor has a good solution to it. I'd gladly be proven wrong though.