Nginx – using Nginx as reverse proxy to apache or stand alone

apache-2.2nginxPHPPROXYreverse-proxy

I've read a lot about this issue (including all threads in this site) and couldn't come to a conclusive decision.

What is considered better (performance and security wise) for very high load sites (millions of users per day):

standalone Nginx + PHP + SQL
Nginx as a revers proxy for Apache + PHP + SQL

What I don't get is – if Nginx can run dynamic content why use Apache at all?

Best Answer

I have 20+ web servers running nginx+php-fpm behind a pair of HAProxy balancers. In my opinion, and from my own experience, this is the optimal setup. Not taking anything away from Apache (I use it for over 10 years), but Nginx simply blows its socks off.

HAProxy is the best open source load balancer. Period. I have tried many, including commercial offerings. I installed nginx on the load balancer as well to offload the SSL. It works like a charm, even under high load.

Splitting all the static content (images, css, js, etc) to separate nginx(s) gives you a further performance boost. HAProxy can send all static requests to a separate server, meaning you have the benefit of parallel requests in your back end systems.

If you do try HAProxy, remember to keep the MAXCONN setting for the web servers to a low (like 20 of 40) value. I see so many posts that have the web server maxconn setting being set to something like 1000 - which will result in HAProxy overloading a node in no time flat.

Related Solutions

Nginx requesting index through reverse-proxy

Add

location = / {
  proxy_pass http://127.0.0.1:8080/test.php;
}

Nginx + php-fpm VS Nginx as a reverse proxy for Apache

Reverse proxying is slower and generally worse, however, some reasons to use it is to maintain (some) compatibility with .htaccess files (which you would have to write (and that isn't always practical) is you use a pure nginx setup) or if you require specific apache modules. (Some may argue that is you have these requirements, it is easier to just use apache.)

PHP-FPM with nginx would be the preferred solution - you get the fast static file serving of nginx and good PHP performance without adding additional overhead, proxying, or the (typically) significant memory usage of apache.
nginx+PHP-FPM is (typically) faster and uses less memory. Nginx + Apache + FastCGI/FPM will still serve static files fast, but will have additional overhead on the dynamic files (not as bad as mod_php, but worse than if you eliminate apache).
You will need a bit of both - nginx would need to know how to deal with the paths (e.g. for serving static files, denying access to .htaccess, etc) and apache will need to know how to handle the files. In some cases, if your .htaccess file doesn't pertain to static files (so every request that needs rewriting is going to go to apache), then it may be acceptable to simply deny access to certain locations, and have apache do the rest via .htaccess - it doesn't seem ideal, will cost a bit in performance, and its reliability is questionable - but it could work on a simple setup).

If you can, go with the straight nginx+PHP-FPM setup. If you can't, while there may be some merits to reverse-proxying, think through the repercussions, especially if you are dependent on .htaccess files.

Best Answer

Related Solutions

Nginx requesting index through reverse-proxy

Nginx + php-fpm VS Nginx as a reverse proxy for Apache

Related Topic