Nginx front-end scheduling server overview

1, you can use the nginx front-end for a lot of complex configuration, these configurations used to be in Squid can not be done or more troublesome, such as anti-theft chain for the directory.

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

3, because nginx efficiency is higher than squid, so in some cases you can use the nginx cache to reduce the pressure of squid.

4, can achieve url hash and other allocation strategies.

5, you can open gzip compression at the front end, so that the latter squid cache is purely uncompressed documents, can avoid a lot of unnecessary penetration.

6, because the stability of nginx is relatively high, so lvs do not need to be adjusted frequently, can be adjusted by nginx.

7, Squid file open number by default 1024 is more than enough, but the processing of requests can not be less.

8, can enable nginx log function instead of squid, so real-time traffic statistics can be accurately located to the url, no longer need to use low-efficiency grep to filter.

9, because nginx's load capacity is higher than squid, so when using lvs shunt, you don't have to be particularly balanced, the probability of a single point of failure is relatively low.