What are the downsides to this approach vs reactive joins(with package like publish composite)? What about just publishing the count number through Collection.find().count() cursor, is it still slow? For the author field, does it really improve performance by that much by embedding instead of joining?
I am trying to figure out how much RAM i could save by denomalizing because subscription to many collections at one time could be costly for meteor.
If you user change his name, you have to update the name of the user collection but also each video (usually with a meteor method, since the video are probably not published) pertaining to this user. There is the risk that you forget to do that for each operation.