Have Geek Brain

Windows / .NET load balancing and balancing

Is there a proven Windows friendly or even .NET native load balancing / load balancing utility out there with the HA Proxy? We have a .NET stack product and one item we pop off the stack is for load balancing.

We need something with custom distribution rules - possibly a subdomain - that NLB doesn't seem to offer. If it integrates directly with .NET or offers an open API called web services, so much the better!

Thanks in advance!

Clarification: we need to arrange boxes logically. This is not just a cluster / failure / replication scenario.

Further clarification: we are the home of the WCF. We already have a custom router and inspectors on our grid. However, we need a distribution on the frontend where HA Proxy currently lives in our architecture. However, we need something that we don't need to write and then heck check out, since we are about to finalize the release and we have no loops to check something down to the HA proxy level.

Solution for candidates: I was previously unaware of IIS7 + Request Routing (ARR) which uses the URLRewrite module. I'm not familiar with anyone who can talk about ARR performance and stability, maybe Stacker can help me?

+2


a source to share


2 answers


I've been using Application Request Routing for several months now, although more for reverse proxying than load balancing or farm management at the moment.

This is definitely handy when you're starting out with a 100% Microsoft stack.

I can't talk about performance yet, at least not in a broad sense. Using it as a proxy does not result in a noticeable performance hit, but it introduces a very rare 502, apparently when the content server takes longer to respond than the ARR controller is configured to timeout.



ARR looks extensible enough to integrate with customers, with integration with third-party hardware like Citrix or F5, but I haven't fully explored this.

I didn't see "definite", "no" "regular" stability issues, but there was some IIS vulnerability that could be related to ARR. Unexplained errors that go away with an application pool reboot or server reboot.

None of the minor problems allowed to enter production. None of the minor issues encountered were demo for customers.

+1


a source


With .NET 4.0 we get a WCF Routing Service that looks like a software based proxy that we get out of the box that can be used for load balancing. It can do content based routing, protocol mediation (tcp / ip-> http or https-> http) and can probably be tweaked in some way.

Some resources to get started:

You can always start skating on your own using these articles from Bustamante:



NTN,

Z

-1


a source






More articles:


All Articles