Compare the advantages and disadvantages of Apache and Nginx

Summary:Comparison of the advantages and disadvantages of Apache and Nginx 1. Advantages of nginx over apache: Lightweight, it also serves as a web service 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...

Comparison of the advantages and disadvantages of Apache and Nginx #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
Active community , various high-performance modules are produced quickly
Advantages of apache over nginx:
rewrite, more powerful than nginx's rewrite
There are so many modules, basically everything you can think of can be found
Less bugs, nginx's There are relatively many bugs
Super stable
The reason why it exists is that, generally speaking, nginx is used for web services that require performance. If you don't need performance and just want stability, then use apache. 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 epoll does not win in all cases. 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 virtual host business owners in the United States. It can support responses of up to 50,000 concurrent connections. Thanks to Nginx for We chose epoll and kqueue as the development model.
Nginx as a load balancing server: Nginx can not only directly support Rails and PHP programs internally to serve external parties, but also support external services as an HTTP proxy server. Nginx is written in C , 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 was also to serve as a mail proxy server) , Last.fm describes a successful and wonderful usage 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 very easy to start, and can almost Achieve 7*24 uninterrupted operation, even if it runs for several months, there is no need to restart. 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’s support for PHP is relatively simple, Nginx needs to be used with other backends
Apache has more components than Nginx
Now Nginx is the first choice for web servers

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 It is good at processing static files and consumes less memory. But there is no doubt that apache is still the current mainstream and has many rich features. So it still needs to be matched. Of course, if it is determined that nginx meets the needs, then using nginx will be a more economical way.

6. Judging from personal past usage, the load capacity of nginx is much higher than that of apache. *The new server also uses nginx. 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. Nginx is only suitable for static and reverse requests.

8. From my personal experience, nginx is a very good front-end server with very 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. It has been developed longer than nginx and has fewer bugs. However, apache has the disadvantage of not supporting multi-core processing loads. It is recommended to use nginx as the front end and back end. Use apache. It is recommended that large websites use the cluster function of nginx

9. There are two main reasons why Nginx is better than apache: 1. Nginx itself is a reverse proxy server 2. Nginx supports 7-layer load balancing; others, of course, Nginx may support higher concurrency than apache, but according to NetCraft statistics According to statistics in April 2011, Apache still accounts for 62.71%, while Nginx is 7.35%. Therefore, in general, Aapche is still the first choice for most companies, because its mature technology and development community already have very good performance. .

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, maintaining connections, 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. It is the most popular. Why? Most people are too lazy to update to nginx or learn new things

12. For nginx, I like that its configuration file is very concise. Regular configuration makes many things simple and efficient. It takes up less resources and has proxy functions. Powerful, very suitable for front-end response server

13. Apache has advantages in processing dynamics. Nginx has better concurrency and low CPU memory usage. If rewrite is frequent, then Apache is the best choice

The above is the detailed content of Compare the advantages and disadvantages of Apache and Nginx. For more information, please follow other related articles on the PHP Chinese website!