nginx requires you to proxy everything, with Apache you can serve most of the website on that server and proxy away only a small part. Damn useful if you want to run something that needs its own http server (like, python-tornado) yet you don't want to give it a separate subdomain.
I think that's not true. You can delegate every location you want to a different server or serve it directly. You know there's this "location" directive in config. Nginx is very flexible.
If you do that, you pay full passthrough costs for every single URL -- parsing, 587598237592 (approximately) context switches, ferrying data between two userspace processes, etc. With Apache, you suffer that only for URLs you actually need to proxy.
This is more BS. Please go set up an actual production environment with nginx. Heck, go set up the environment with a single server that (1) serves sites directly via nginx, (2) proxies some requests back to other servers on your network, (3) does caching of static assets via nginx, (4) does PHP/FastCGI (there are similar setups for Perl, Python, etc). Then go run some actual performance tests.
Basically, you have zero knowledge of nginx, and you're trying to prop up a failed position with senseless babbling
The faster I go, the behinder I get.
-- Lewis Carroll
Use nginx? (Score:5, Interesting)
Why would anyone use Apache as a reverse proxy anyway?
I mean, there's nginx, and it runs circles around Apache as far as I know.
Re: (Score:3, Insightful)
nginx requires you to proxy everything, with Apache you can serve most of the website on that server and proxy away only a small part. Damn useful if you want to run something that needs its own http server (like, python-tornado) yet you don't want to give it a separate subdomain.
Re: (Score:2)
Re:Use nginx? (Score:4, Informative)
If you do that, you pay full passthrough costs for every single URL -- parsing, 587598237592 (approximately) context switches, ferrying data between two userspace processes, etc. With Apache, you suffer that only for URLs you actually need to proxy.
Re: (Score:0)
In both nginx and apache you can select what you proxy by URL. So if that it is a problem in nginx it is a problem in apache too.
Re: (Score:0)
This is more BS. Please go set up an actual production environment with nginx. Heck, go set up the environment with a single server that (1) serves sites directly via nginx, (2) proxies some requests back to other servers on your network, (3) does caching of static assets via nginx, (4) does PHP/FastCGI (there are similar setups for Perl, Python, etc). Then go run some actual performance tests.
Basically, you have zero knowledge of nginx, and you're trying to prop up a failed position with senseless babbling