Why it is worth switching to use nginx?

Very often, every webmaster asks himself the question - “Is it worth it to switch to using the nginx web server?"

I will give simple and understandable reasons for each webmaster, not a techie. We presume that the most popular web server for hosting is apache. Go to the use of nginx, we can on any platform - Linux, * BSD, Sun, Windows, and when using any web server - Apache, IIS, etc. Of course, it should be borne in mind that there are specific tasks for which nginx is not needed (consider this when writing comments).

There are many pros and cons.
')
Nginx allows you to:

• reduce the consumption of system resources on the server (less memory, less CPU load)
• to speed up the delivery of content for visitors, and this is a "plus" so that the visitor returns once more to your site.
• reduce bandwith consumption, due to content compression (who is critical to fit into the hosting limits)

Nginx is very flexible in configuration and can be used with any control panel (on some VPS, for example, rusonyx - this is done through ****)

Want more happy visitors for your site - use nginx, oh wisely;)

And now, let's find out - “And what prevents each webmaster from switching to nginx?”

I now, I will describe the main arguments "against" the transition to nginx, which prevent the massive transition to the use of nginx:

• Apachev.htaccess does not work (this is solved either by using apache as a backend or by describing the rewrite rules in the nginx config)
• cgi-scripts do not work (in nginx there is no cgi support, only through backends with cgi support - apache, lighttpd, etc.)
• not everyone wants to understand the nginx settings (but what’s stopping them from turning to specialists who, for a normal salary, will do everything in the best possible way?)
• some difficulty in self configuration of nginx with apache

This is not a complete list, but its main part.