Three ARR Back End Binding Options–Week 35

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.