Menu
I have a very large collection (~40000 documents with ~20-25 fields including array-fields with a set of ~500 items in) and ~2000 subscribers (they are just bots now).
So it's really hard work on client when user subscribe on whole collection (excluding some fields in server's publish) and use Collection.find with custom filters, sort and order
I tryed to use publish with options: i.e. client-defined filters & etc. But in this case I have too many memory leaks on server and epic fail :) after a few hours.
Can anyone advise some publish-subscribe schema for that kind of collections? I do not ask for clear solution but some useful thoughts
Thanks
878
Common methods of collecting big data endpoint devices within IoT ecosystems; second- and third-party sources such as marketing firms; social media posts from existing and prospective customers; multiple additional sources like smartphone locational data; and.
publish on the server with two parameters: the name of the record set, and a publish function that Meteor will call each time a client subscribes to the name. Publish functions can return a Collection. Cursor , in which case Meteor will publish that cursor's documents to each subscribed client.
You might want to try https://github.com/alethes/meteor-pages
It has:
Incremental subscriptions. Downloads only what's needed, not the entire collection at once. Suitable for large datasets.
89
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
