What would be the most resource-efficient way to handle publications?
Say, I have a gigantic Items collection. Initially, user sees only 30 items, based on user’s cityId; items are from all Categories and sorted by date.
He can switch to other city and see completely different 30 items.
He also can choose a Category and see 30 items for this category - they may or may not overlap with the items he saw initially.
Of course, there is pagination to see next 30 items.
I’ve read somewhere that a ‘detailed’ pub concept is more expensive than ‘general’ pub, because when 10k users subscribe, server has to serve them different sets of data, query the db and so forth…