Comparison of the advantages and disadvantages of Apache and Nginx

http://blog.csdn.net/xifeijian/article/details/17385741

1. Advantages of nginx over apache:
Lightweight, can also serve web services, and takes up less memory and resources than apache
Anti-concurrency, nginx processes requests asynchronously and non-blockingly, while apache is blocking. Under high concurrency, nginx can maintain low resources, low consumption and high performance.
Highly modular design, writing modules is relatively simple.
The community is active and various High-performance modules are produced quickly

Advantages of apache over nginx: rewrite, more powerful than nginx's rewrite

Dynamic pages

There are so many modules that you can basically find everything you can think of
Fewer bugs, nginx has relatively more bugs

Super stable

The reason for existence is, generally speaking, for web services that require performance, use nginx. If you don't need performance and just want stability, then use apache. The various functional modules of the latter are implemented better than the former. For example, the ssl module is better than the former and has more configurable items. One thing to note here is that the epoll (kqueue on freebsd) network IO model is the fundamental reason for nginx's high processing performance, but not all situations are epoll's winner. If it provides static services, only a few file, apache's select model may be more performant than epoll. Of course, this is just an assumption based on the principles of the network IO model. The real application still needs to be tested before talking about it.
2. As a Web server: Compared with Apache, Nginx uses fewer resources, supports more concurrent connections, and reflects higher efficiency. This makes Nginx especially popular with virtual host providers. In the case of high connection concurrency, Nginx is a good alternative to the Apache server: Nginx is one of the software platforms often chosen by bosses in the virtual host business in the United States. It can support responses of up to 50,000 concurrent connections. Thanks to Nginx for this We chose epoll and kqueue as the development model.
Nginx as the load balancing server: Nginx can not only directly support Rails and PHP programs internally to provide external services, but also support external services as an HTTP proxy server. Nginx is written in C, regardless of Both system resource overhead and CPU usage efficiency are much better than Perlbal.
As a mail proxy server: Nginx is also a very excellent mail proxy server (one of the earliest purposes of developing this product is also as a mail proxy server), Last.fm description A successful and wonderful use experience.
Nginx is a server that is very simple to install, has a very concise configuration file (it can also support perl syntax), and has very few bugs: Nginx is particularly easy to start, and can be almost 7*24 uninterrupted Even if it runs for several months, it does not need to be restarted. You can also upgrade the software version without interrupting the service.
3. Nginx configuration is simple, Apache is complex
Nginx static processing performance is more than 3 times higher than Apache
Apache Support for PHP is relatively simple. Nginx needs to be used in conjunction with other backends.
Apache has more components than Nginx. Now Nginx is the first choice for web servers. Many large Internet companies have already used nginx.
4. The core difference is that apache is a synchronous multi-process model, and one connection corresponds to one process; nginx is asynchronous, and multiple connections (10,000 levels) can correspond to one process.

5. nginx handles static files well. It consumes less memory. But there is no doubt that apache is still the mainstream and has many rich features. So it still needs to be matched. Of course, if it is determined that nginx suits the needs, then using nginx will be a more economical way.

apache has It inherently does not support multi-core processing and has the disadvantage of useless load. It is recommended to use nginx as the front end and apache as the back end. Large websites are recommended to use the cluster function that comes with nginx

6. From the usage point of view, the load capacity of nginx is much higher than that of apache. Moreover, after changing the configuration of nginx, you can -t test whether there is any problem with the configuration. When apache restarts, it is found that the configuration is wrong and it will crash. I will be very careful when making changes. Now there are many cluster sites. The front-end nginx is anti-concurrency, and the back-end apache cluster , the cooperation is also good.

7. It is useless for nginx to handle dynamic requests. Generally, apache is required to handle dynamic requests, and nginx is only suitable for static and reverse requests.
8. nginx is a very good front-end server with good load performance. It is effortless to open nginx on Laoben and use webbench to simulate 10,000 static file requests. Apache has good support for languages ​​​​such as php. In addition, apache has a strong support network and has been developed for a longer period of time than nginx.
9. There are two main reasons why Nginx is better than apache: 1. Nginx itself is a reverse proxy server 2. Nginx supports layer 7 load balancing; in addition, of course, Nginx may support higher concurrency than apache.
10. Your needs for web server determine your choice. In most cases, nginx is better than APACHE, such as static file processing, PHP-CGI support, reverse proxy function, front-end Cache, connection maintenance, etc. In the Apache+PHP (prefork) mode, if PHP processing is slow or the front-end pressure is high, it is easy for the number of Apache processes to surge, resulting in a denial of service.
11. You can take a look at the nginx lua module: https://github.com/chaoslaw... Apache has more modules than nginx. Apache can be implemented directly with lua. Apache is the most popular, why? Most people are too lazy to update to nginx or learn new things.
12. For nginx, its configuration file is written very concisely. Regular configuration makes many things simple and efficient. It takes up less resources and has powerful proxy functions. It is very suitable for front-end response servers.
13. Apache has advantages in processing dynamics. Nginx has better concurrency and low CPU memory usage. If rewrite is frequent, Apache is more suitable.

Source of this article: collected and organized from the Internet

The above introduces the comparison of the advantages and disadvantages of Apache and Nginx, including aspects of the content. I hope it will be helpful to friends who are interested in PHP tutorials.