Hello, there. Hope you are doing well.
As a senior Django developer, My answer would be like this regarding your questions.
1. Normally, I used two methods for it.
- No matter what strategy you pick, or what is your business model, always use one, and only one Django model to handle
the authentication.
- Never user the built-in Django User model directly, even if the built-in Django User implementation fulfill all the requirements
of your application.
2. Using Django to download large files isn't really recommended. Usually you'd have a front-end multiplexer such as NginX,
and use Django only to validate the file.
Then, if the download is validated, you'd issue a signal to the multiplexer. For NginX, you can set up a special header ("X-
Accel-Redirect") to point to the true location of the local file. Django will only serve a few bytes, and all the heavy lifting will be
taken up by NginX; at the same time the original URL will be that of Django, so that it is not possible to bypass security.
3. I think django framework has a async problems. To avoid this, we are using the redis server.
Reach out to me on here so that and we can discuss details.
Looking forward to hearing from you.
Regards.
Goran