Application Request Routing CTP1 has been released.
Application Request Routing (ARR) was just released yesterday (July 2, 08) and I wanted to highlight some of the core scenarios that the CTP1 release enables. (You can get more information on ARR and helpful walkthroughs here.)
-
3 tier deployment architecture: As the name indicates, there are 3 tiers: a web tier, an application tier, and a data tier. In this scenario, the web tier, where ARR is installed, would serve both a proxy based load balancer and a content server that serves static contents. The web tier inspects the incoming requests, and based on the routing rules, it can either decide to serve the contents from itself, or to route them to the application tier servers, which would serve the dynamic contents based on the business logic. This deployment architecture helps to scale the application tier by reducing the amount of traffic that are routed to the application tier servers. The goal would be to maximize and better utilize the server resources in the application tier. In addition, you can now scale the web tier and the application tier independently. You can learn more about how you can configure ARR in this scenario at this walkthrough.
-
Software load balance: This is a sub-scenario of the first scenario above. Instead of splitting the requests based on HTTP header or server variable, it forwards all requests to the content servers. In this scenario, ARR is being used as a reverse proxy based load balancer. You can learn more about how to use ARR in this scenario at this walkthrough.
-
Shared hosting using "host name affinity": This is a feature that is specifically designed for shared hosters. The overview of this scenario is well documented in this article. This is an exciting feature that simplifies how the shared hosters provide their services and also enables a straightforward scalability and availability story. You can learn more about how to use ARR in this scenario at this walkthrough.
Downloads:
Support:
The support is provided via ARR form which can be found at http://forums.iis.net/1154.aspx.