The advantages of Nginx relative to Apache httpd:
1 - Lightweight, similarly web service, consumes less memory and resources than Apache 2 - anti-concurrency, Nginx processing requests are asynchronous non-blocking, and Apache is blocking type, in high concurrency under the Nginx Ability to keep low resource consumption high performance 3 - highly modular design, writing modules relatively simple 4 -Community active, a variety of high-performance modules produced quickly AH
The advantages of Apache httpd relative Nginx:
1 - rewrite, more powerful than Nginx rewrite 2 - Super module, basic thought can find 3 - less bug, Nginx bug Relatively high 4 -ultra-stable
cache caching; Cache is generally used to hold some frequently accessed objects or data;
High-performance server accelerator; 1, Varnish High-performance open-source reverse proxy and HTTP accelerator; 2, Squid is a high-performance proxy cache server; same point: all open source, do reverse proxy; different points: Varnish stability ; Access is fast; Squit is cached from the hard disk. Varnish can support more concurrent links, or it can support more TCP links. However, if the power outage, the back-end server caused great pressure; Varnish CPU IO and memory resource overhead are higher than squid in the concurrency state. squid supports not only HTTP protocols, but also FTP, Gopher, SSL, and WAIS protocols. Unlike the generic proxy cache software, squid handles all client requests with a single, non-modular, I/o driven process. Squid caches internet Local data 3, resin
is a very popular application server that supports load balancing, increases the reliability of Web sites, can be used for JSP programming, and Resin providesthe fastest JSP/Servlets running platform. You can useApache +resin to improve performance with Apache's caching capabilities. 4, Memcached open source free distributed memory object cache system, to reduce the database load, and improve the performance of the system;; Memcache is a memory cache that caches objects in memory, which is read in memory by the API, and can be used to respond to Web sites.
WEB Server Accelerated Cache comparison