Nginx VS Apache

1, the advantages of nginx with respect to Apache:
Lightweight, same Web service, consumes less memory and resources than Apache
anti-concurrency, Nginx processing requests are asynchronous non-blocking, and Apache is blocking type , in high concurrency, nginx can keep low resource consumption and high performance
Highly modular design, relatively simple to write modules
Community active, a variety of high-performance modules produced quickly AH
The advantages of Apache with respect to Nginx:

Rewrite, stronger than Nginx's rewrite

Dynamic pages

The module is too much, the basic thought can be found
Fewer bugs, nginx bugs are relatively large

Ultra-Stable

Existence is the reason, in general,Web services that require performance, using Nginx. If performance is not required for stability, then Apacheit. The latter of the various functional modules implemented than the former, such as the SSL module is better than the former, more configurable items. One thing to note here is that Epoll (FreeBSD is kqueue) network IO Model is the fundamental reason for the high performance of nginx processing, but not all cases are epoll victory, if you provide static services only a few files, Apache Select Models may be more performant than Epoll. Of course, this is just a hypothesis based on the principle of the network IO model, and the actual application still needs to be measured.

2, as a WEB server: using less resources than Apache,nginx, supporting more concurrent connections, reflecting higher efficiency, which makes Nginx particularly popular with virtual hosting providers. In the case of high connection concurrency, Nginx is a good alternative to Apache server: Nginx in the United States is a virtual hosting business owners often choose one of the software platform. Capable of supporting responses of up to 50,000 concurrent connections,We thank Nginx for choosing Epoll and Kqueue as the development model.
Nginx as a Load Balancer server: Nginx can either directly support the internal Rails and PHP programs outside the service, also can support as an HTTP proxy server external services. Nginx is written in C, which is much better than Perlbal, both in terms of system resource overhead and CPU efficiency.
As a mail proxy: Nginx is also a very good mail proxy server (one of the first to develop this product is also as a mail proxy server), Last.fm describes the success and wonderful use of experience.
Nginx is a very simple installation, the configuration file is very concise (also can support Perl syntax), Bugs very few servers: Nginx boot is particularly easy, and can be almost uninterrupted operation, even if the run for several months do not need to restart. You will also be able to upgrade the software version without interruption of service.

3, Nginx Configuration concise, Apache complex
Nginx static processing Performance 3 times times higher than Apache
Apache support for PHP is relatively simple, Nginx needs to cooperate with other backend
Apache has more components than Nginx
now Nginx is the preferred Web server

4, the most important difference is that Apache is a synchronous multi-process model, a connection corresponding to a process; Nginx is asynchronous, multiple connections (million levels) can correspond to a process

5,nginx processing static file is good, consumes less memory . But Apache is undoubtedly still the mainstream, with a lot of rich features. So it needs to be paired. Of course, if you can be sure that Nginx is suitable for your needs, then using Nginx will be a more economical approach.

Apache does not support multi-core to download the Chicken rib shortage, recommend using Nginx to do the front end, the back end with Apache. Large Web site suggestions for the use of nginx-generation cluster function

6, from the personal past use of the situation, nginx load capacity is much higher than Apache. The newest server also changed to Nginx. and Nginx change the configuration can be-t test configuration is not a problem, the Apache restart when the configuration error found, will be very crash, change will be very cautious now see a lot of cluster station, front-end nginx anti-concurrency, back-end Apache cluster, with good.

7,nginx processing dynamic request is chicken, general dynamic request to Apache to do, nginx only suitable for static and reverse.

8, from my personal experience to see, Nginx is very good front-end service, the load performance is excellent, in the old Ben on the Nginx, with Webbench simulation 10,000 static file Please do not have the difficulty. Apache's support for languages such as PHP is good, and Apache has a strong support network, which is more time-intensive than Nginx,

9, Nginx is superior to Apache's main two points: 1.Nginx itself is a reverse proxy server 2.Nginx support 7-tier load balancing; Other of course, nginx may support higher concurrency than Apache, but according to Netcraft statistics, April 2011 Statistics, Apache still occupies 62.71%, and Nginx is 7.35%, so always, Aapche is still the majority of companies first, because its mature technology and development community has also been very good performance.

10. Your need for Web server determines your choice. In most cases, Nginx is superior to Apache, such as static file processing, php-cgi support, reverse proxy function, front-end cache, maintenance connection, and so on. In apache+php (prefork) mode, if the PHP process is slow or the front-end pressure is very high, it is easy to get a spike in the number of Apache processes, thereby denying service.

11, can look at the Nginx Lua module: Https://github.com/chaoslaw...apache more than Nginx module, can be directly implemented with LUA Apache is the most popular, why? Most people don't bother updating to nginx or learning new things.

12, for Nginx, I like it configuration file written very concise, regular configuration makes a lot of things easy to run high efficiency, less resources, powerful proxy, very suitable for the front-end response server

13, Apache in processing dynamic has advantages, nginx concurrency is better, CPU memory consumption is low, if rewrite frequent, it is Apache Bar

This article is from the "Linux Revolution" blog, so be sure to keep this source http://kaibinyuan.blog.51cto.com/7304008/1567612

Nginx VS Apache