Nginx as the frontend webcache System

Author Ayou: http: sudone.com advantages of this structure: 1. You can use the nginx front-end to perform many complex configurations. These configurations were previously not feasible or difficult to do in squid, for example, anti-leech for directories. 2. The nginx front-end can directly forward some requests that do not need to be cached. 3. Because nginx is more efficient than squid, some

Author Ayou: http ://SuDone.com/

 

Advantages of this structure:

1. You can use the nginx front-end to perform many complex configurations.IdIt cannot be done or is difficult to do, such as anti-leech targeting directories.

2. The nginx front-end can directly forward some requests that do not need to be cached.

3. Because nginx is more efficient than squid, you can use nginx cache to reduce squid pressure in some cases.

4. url hash and other allocation policies can be implemented.

5. You can enable g at the frontend.ZipCompressionIn this way, the squid cache is purely non-compressed, which can avoid unnecessary penetration.

6. Because nginx has high stability, lvs does not need to be adjusted frequently. you can adjust it through nginx.

7. The number of squid files opened is more than 1024 by default, but there are no fewer requests to process.

8. You can enable the nginx log function to replace squid. In this way, the url can be precisely located during real-time click statistics, and inefficientGrepTo filter.

9. Because nginx has a higher load capacity than squid, you do not need to be balanced when using lvs for traffic distribution. The probability of single point of failure is relatively low.

CurrentlyArchitectureFurther detailed tests are required. sudone.com currently uses this architecture.