September 2011 - Posts
You can find this week’s video here.
This video covers two specific tricks to allow the Application Request Routing (ARR) and Web roles to share the same server. This is useful if you have multiple servers and can't setup dedicated servers for ARR, or even if you want to leverage ARR's functionality on the same server as the website.
In recent weeks we’ve been looking at Application Request Routing (ARR) and how to use it in your environment. Since it is a service that lives on a Windows server, it is possible to have the ARR role on the same server(s) as the web role.
My recommendation is to give dedicated servers to the ARR role if possible. The two reasons why I recommend this is for 1) troubleshooting reasons since it’s a bit more difficult to troubleshoot URL Rewrite rules when both roles are on the same server and 2) to protect the ARR servers (very low failure rate + low performance requirements) from the web servers (higher failure rate + higher performance requirements).
However, there are still valid reasons to collapse the two roles in a single server, or into multiple ARR+WEB servers. This video discusses this option and shows two tricks on how to do this successfully.
This is now the 12th week in a mini-series on web farms, and the 37th week of the entire series. You can view past and future weeks here: http://dotnetslackers.com/projects/LearnIIS7/
You can find this week’s video here.
You can find this week’s video here.
This week's video shows a specific trick to allow a reverse proxy—Application Request Routing in this case—how to use only one IP address per web servers while supporting many distinct sites. This is extra useful if you have a wildcard domain name, or a large number of domain names pointing to a VIP, and you have multiple sites to manage.
I want to show you a trick that allows you to use just a single IP address per web server, no matter how many sites you have. And, you can do this with wildcard domain names or large lists of domain names—with ease.
Last week we talked about the three web node binding options. They are: A) by host header, B) by IP Address, and C) by port. They work for many situations, but what if you have many sites and many servers and you want your virtual IPs (VIPs) to accept traffic for any domain name? For example, imagine that you want *.mycity.com to point to a dedicated IP address, and you manage multiple sites like this.
This week I cover this specific situation and show a handy trick to manipulate the HTTP_HOST (domain name) on the way through to make a potentially unruly situation much more manageable.
This is now the 11th week in a mini-series on web farms, and the 36th week of the entire series. You can view past and future weeks here:http://dotnetslackers.com/projects/LearnIIS7/
You can find this week’s video here.
You can find this week’s video here.
ARR and other reverse proxies need a way to connect to the actual web nodes. Like other reverse proxies, Microsoft’s free load balancing solution—Application Request Routing (ARR)—needs a way to connect to the sites on the actual web nodes.
This week I cover different options available to managing the site bindings for the sites per server. If you have a single site, it’s straight forward, but once you start adding sites and servers, then you need to plan how to manage the binding sprawl.
Consider an environment using ARR which have 5 sites on 5 servers. That fairly small example has 25 separate sites on the web servers plus another 5 sites on the ARR load balancer. How will you handle the bindings between the ARR servers and web servers. You have three primary options. They are: 1) Host Headers, 2) Unique IP Addresses or 3) Unique ports. This week I cover the three methods and how to plan and configure each option. You can then decide which option works best for you.
This is now the 11th week in a mini-series on web farms, and the 35th week of the entire series. You can view past and future weeks here:http://dotnetslackers.com/projects/LearnIIS7/
You can find this week’s video here.
More Posts