用 IIS 7、ARR 与 Velocity 建设高性能的大型网站.docVIP

用 IIS 7、ARR 與 Velocity 建设高性能的大型网站 本帖是研讨会中的一些杂记，搭配一些官方的文档，经整合归纳后，介绍 IIS 7 如何搭配新一代的 ARR (Application Request Routing)，建置 Server Farm 并达到比过去 NLB 更优的 Load Balancing 功能，此外还介绍微软新一代的分布式缓存技术 Velocity。 过去及目前 Windows Server 中的 NLB (Network Load Balance, 负载均衡) 其缺点: 用软件做的 NLB 功能较少。 网络流量全挡在 NAT，而 NLB 都在内部网络的 Windows Server / IIS 上。 只做到网络协议的 Layer 4。 没有 Health Monitoring，无法知道 Web Server / AP 的目前情况；即使网站当机了，NLB 仍会将流量持续导引至此。 较适合 Client 架构，较不适合 Web AP。 此外，若改用硬件做 NLB，虽然性能较佳，但价格较贵，且弹性较低。 因此 ARR (Application Request Routing) for IIS 7 出现了，其功能包括 [1], [2]: Microsoft Application Request Routing Version 1 for IIS 7 is a proxy-based routing module that forwards HTTP requests to content servers based on HTTP headers and server variables, and load balance algorithms. Application Request Routing (ARR) can be used to: Increase application availability and scalability. Better utilize content server resources. Facilitate application deployment including pilot management and A/B testing. Lower management costs and create opportunities for shared hosters. Application Request Routing relies on the URL rewrite module to inspect incoming HTTP requests to make the routing decisions, and therefore, the URL rewrite module is required to enable Application Request Routing features. ARR 的特性： HTTP-based routing decisions:Unlike hardware load balancers that make the routing decisions at the IP level, Application Request Routing makes the routing decisions at the application level. Working with the URL rewrite module, powerful routing rules can be written based on HTTP headers and server variables.达到网络协议的 Layer 7。 Load balance algorithms:A user-selected load balance algorithm is applied to determine which content server is most appropriate to service HTTP requests. Six algorithms are provided.提供六种负载均衡的算法，可供网管人员选用。 Health monitoring:Both live traffic and specific URL tests are used to determine the health of content servers. A set of configuration parameters are provided to define the meaning of serve