ARR Health Checks–Week 34

You can find this week’s video here.

Application Request Routing (ARR) is used as a load balancer (reverse proxy) for highly available websites. This week I cover health checks in ARR and lay out a few principles that will help you be more effective in your web farm environment.

Properly planning health checks is important with any load balancer, and Application Request Routing (ARR) is no exception.

Health checks are used to check the state of your servers so that if a server fails, it is automatically taken out of rotation, and then added back again when it has recovered. At first glance it may seem that minimal thought needs to go into planning your health checks, but that’s not the case. Through my own mistakes in the early days of working with web farms I’ve come to the realization that you shouldn’t test your database server, web service calls or other external dependencies with the health checks. Instead you should only test the web server, app pool and site. This video answers why to this question, and more.

This is now the 10th week in a mini-series on web farms, and the 34th 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.