Running multi-tenant site using a fork of Django tenant schemas with tens of web servers and thousands of tenants....
Piloting a project to implement Channels for real-time notifications, etc. I want to confirm these assumptions: 1. Channels really has no support for multi-tenant, I will have to roll my own. 2. Since uWSGI is serving us well and (at this point) I wouldn't trust Daphne to serve HTTP, I've got split paths in NGinx for uWSGI and ASGI. 3. We are running RabbitMQ, so we have to cluster it and implement channels using asgi_rabbitmq (Redis would just add yet another moving part) 4. Plan on significant additional resource requirements on the web server and serious scaling challenges. Are their any other non-Channels options, or is it the really the only game in town? Thanks. -- 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/aae2725b-d873-40fd-ae09-d1668ab9e727%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
