Is it reasonable to have one pub/sub channel/topic per post on a community platform?
As I understand it, a channel/topic in a pub/sub architecture is used to keep track of which subscribers to notify when an event occurs. E.g. If I comment on a post I can subscribe to the channel for that post and receive notifications regarding that post (reactions and comments ). But that would mean that a channel is created any time a post is created, resulting in a potentially huge number of channels which doesn't sound reasonable when I look at the pricing models of different Cloud services for pub/sub? Even a channel for each user would generate fairly many channels as the platform grows. Am I missing something or can someone propose a different way to think about channels?
As I understand it, a channel/topic in a pub/sub architecture is used to keep track of which subscribers to notify when an event occurs. E.g. If I comment on a post I can subscribe to the channel for that post and receive notifications regarding that post (reactions and comments ).
But that would mean that a channel is created any time a post is created, resulting in a potentially huge number of channels which doesn't sound reasonable when I look at the pricing models of different Cloud services for pub/sub?
Even a channel for each user would generate fairly many channels as the platform grows. Am I missing something or can someone propose a different way to think about channels?
What's Your Reaction?
