Thanks for that link. I did a bit of reading, and found this [1].
> These are the main bottlenecks when scaling Meteor, and they introduce two main issues: 1. The polling and comparing logic takes a lot of CPU power and network I/O. 2. After a write operation, there is no way to propagate changes to other Meteor instances in real-time. Changes will only be noticed the next time Meteor polls (~10 seconds).
This seems like quite a limitation. So I wonder if there are any libraries out there that successfully solved this?