I thought that the fact redis was being used (or any distributed store)
wouldn't make this an issue, so basically redis is used to be able to scale
out the workers but the web sockets listener can't currently be scaled out.
The main reason of the question was about being able to deploy everythin
Yes, this is a problem, and as it says it would only work for some site
designs (where you're OK with sharding the live userbase). We're fixing
this architectural issue in the next major Channels release, but it's going
to take a little time.
Andrew
On Mon, Aug 7, 2017 at 4:21 AM, Cristiano Coelh
2 matches
Mail list logo
