For some reason my original question got lost.

I don't quite understand this part: 

The fundamental difference is that the group mechanic requires all servers 
serving the same site to be able to see each other; *if you separate the 
site up and run it in a few, large clusters, messages to groups will only 
deliver to WebSockets connected to the same cluster.* For some site designs 
this will be fine, and if you think you can live with this and design 
around it (which means never designing anything around global notifications 
or events), this may be a good way to go.

Does this mean if I run the ASGI/Interface server on multiple servers (load 
balanced), channels won't properly work since any broadcast to a group will 
only send messages to clients connected to that cluster and not others? 
What's the point of using redis? I would assume the whole groups concept 
would be able to broadcast messages back to every client regardless of how 
many web sockets servers you have running.

What I'm trying to find out is, if I run multiple servers that are deployed 
automatically and load balanced (such as amazon elastic beanstalk), where 
each server runs a standard django app, and also django channels both 
interface and workers, would it still work, or the fact that there might be 
multiple servers listening to the web sockets connections will pretty much 
break any messages broad casting? The wording from the documentation seems 
a bit unclear.

You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
To view this discussion on the web visit
For more options, visit

Reply via email to