How to determine best way to subscribe to a collection?

[arvi]

Having many ways to subscribe to a collection, how do I determine which is best to apply in a particular case? What can be my basis for deciding?

1. Meteor.subscribe via Iron Router waitOn option (I’m currently using this approach for all)
2. this.subscribe available in Meteor 1.0.4
3. Meteorhacks subs-manager (just found out about this and I’m curious if the problem being solved here is already covered in the new this.subscribe method)

I’m currently building my first-ever real meteor app and really need some insight, or any suggestions regarding this matter.

Thanks a lot!

[matthewsimo]

This new article by @sashko will help to clarify the publish/subscribe dance - https://medium.com/@stubailo/data-flow-from-the-database-to-the-ui-three-layers-of-meteor-d5e208b466c3 - it’s the latest and has the 1.0.4 features. Hope that helps, GL with your app!

[serkandurusoy]

@arvi the exact same question has been asked on another topic, and here’s my answer:

Template-level subscription patterns in 1.0.4

@sacha wrote a great blog post a while ago on this topic: https://www.discovermeteor.com/blog/template-level-subscriptions/ It explains use cases for template level subscriptions where there also are app/page level subscriptions and concludes exactly like this smile One of the best (and worst!) things about Meteor is that there is often no “right” way to do things. So the best you can hope for is to familiarize yourself with an array of different techniques, and pick the right one at the r…

[arvi]

@matthewsimo @serkandurusoy Thank you so much for the resources. It would really help my subscription approach dilemma