Microsoft has a lot of documentation about their somewhat new load balancing and request routing module for IIS7 located here: http://blogs.iis.net/bills/archive/2009/02/16/iis7-request-routing-and-load-balancing-module-released.aspx, but I'd like to know if anyone has experience using it in production. What are a few pros / cons to using this module instead of another solution such as HAProxy?
We are using it in production for a company info website. And we havnt had any problem at all with it yet. And it works smooth to take down servers and loadbalancing also work nice. Using least reponsetime so one of the server is getting some more requests. We are going to move one of our ecommerce stores also that have alot more trafic then the company info site. So we will see how it works under more heavy load. But our tests have showed that it should handle it without problems
Using it in production at www.orcsweb.com. Absolutely love it! It's so simple and yet so powerful. Every time we try something creative against it, ARR works with that too. IIS7 itself is rock solid too, so building something on top of IIS7 is a great idea.
We've used hardware load balancers for years with great success, but are moving towards ARR for most sites now.
Make sure to use the ARR Helper on the web servers. The 2 reasons are: - IPs from the original user are logged to the logs, and REMOTE_ADDR and REMOTE_HOST are updated to the user's IP - you can use SSL offloading, and the code can't tell the difference
I suggest using it with NLB and create 2 ARR nodes. Set the first node to take all traffic unless the 1st fails. That way the statistics will be on the first node. Use Shared Configuration so that you don't need to manually manage the 2nd node except to import and assign the SSL certs.
Here's a blog post I did with some more info: http://weblogs.asp.net/owscott/archive/2009/08.aspx