Assuming your concern is with a few connections / requests in general, and not users in particular, I should say the following about Django and threads.
Django is definitely thread safe. This is a design consideration that has taken a few people in the past, as the person who follows the development of Django can watch.
For this reason, Django can be deployed in a multi-threaded container, such as the default streaming mod_wsgi that works with the Apache server, and as such has been appreciated by many deployments.
However, there are concerns about how thread-safe any particular Django-based application is, and it depends on individual developers and third-party developers who use best practices.
Django documentation has separate sections on thread safety. For example, class-based documentation specifically mentions that each class-based view has an independent state. In addition, one of the most common problems is custom template tags, like the address in this section . I am sure there are other links on this subject that I am currently skipping, so I would advise you to keep the documentation if your thread safety issues are too great.
source share