ActionCable: Best practices for channel structure?

Hi *,

I’m just wondering if there are any best practices of how to identify which channels to create in larger apps with many different parts (conversations, threads, projects, task-lists, user-status, etc…)

Do you have some sort of general-notifications channel to subscribe for overall-updates? And further then more fine-grained channels for each part / level? For each listing? Even for each model?

Due to individual visibilities a general-notifications channel would mean that there’s at least one personal stream per user. The backend then has to loop over these users and push each message individually… hmmm…

Well, I think basically the question is: What’s the cost of creating/maintaining a channel/stream? :slight_smile: