As bizarre as it may sound, some people would think twice or even 3 times before making their decision.

Simple rule is: web server configuration has to be build in accordance to your software needs or design specifications. Sometimes you may think that your website would work better (faster, withstand more load or even be more secure) if you switch web server configuration (not tuning, but changing software).

Reasons to hold on to Apache are simple: if you run a website that was originally designed to be working with Apache (many popular CMSs do) or maybe you do first steps into the web world. Ahhhh good old friend, Apache…

I’m using WordPress CMS and many plugins are designed to be working well with Apache. WordPress wouldn’t be as popular if not for the plugins variety.

I’ve used a few configurations with WordPress, like LEMP (Nginx, php-fpm, mysql) – is very good out the box, but I’ve spent weeks setting up rules one by one… Many rules I’ve missed simply because when I was installing a new plugin – I did not think that it may be designed with Apache in mind. Every now and then I had to look for the holes and patch them. Then LAMP, well it is what it is isn’t it? LAMP is working, but every time I had many visitors, that didn’t look as pretty, hah… And yes many would argue that I had to tune it more, I gave up…

Now I try Nginx as a Reverse Proxy for Apache, and so far so good. I don’t have to look for every .htaccess in order to move rule to NGINX like I did in LEMP and not scared that I’ve missed something important. When I have few more visitors to my website than I was expecting – nothing major happens.