Django and Apache: mod_wsgi or mod_proxy?

Question

Django

Situation.
In the office there is an Apache on Windows, a self-written php site is running. Due to organizational reasons, it is impossible to change the OS and http-server. The question is, what is the best way to embed a small django application here?
Tried through screw mod_wsgi - works.
The question is, will it work faster / better if you run the application through tornadoweb as a server and configure Apache to proxy through mod_proxy?

Answer 1

As far as I know, django applications run the fastest on nginx + uwsgi, but I'm not sure if it will be deployed on Win
Maybe put a virtual machine on Win? releasing it to a real network, and in it a fast debian.

Answer 2

If you are satisfied with the work of mod_wsgi - leave it. Tornado, if you run a regular wsgi framework on top of it, will not give any advantages. Moreover, it can only get worse.

Answer 3

The most successful, in my opinion, will be nginx, which gives all the static and proxy by domain name to uwsgi (django sites) and apache (everything else). To the Apache it is better to close access from the outside on a straight line. Practice has shown not bad performance (you can get a link and details in a personal, otherwise it’s advertising).
Instead of uwsgi, gUnicorn with gevent workers unexpectedly performed well in practice.