Component Load Balancing in Windows 2003 Servers RRS feed

  • Question

  • Hi, I'm looking for Load Balancer for our COM application servers which uses the least busy server based on resource (CPU) usage.

    Our COM components perform time consuming computations, therefore Network Load Balancing (NLB) doesn't work for us at all as it is based on incoming packets and doesn't take the CPU usage into account, so it redirects all requests usually to one single server...

    The application worked happily in Windows 2000 server environment using Application Center's Component Load Balancing (CLB). Since the servers were migrated to Windows 2003, CLB feature is unavailable as it is for Windows 2000 only and MS stopped supporting Application Center anyway. I would consider further upgrading e.g to 2008 server if it helped.

    I would be very surprised if Microsoft didn't provide CLB-like solution, however having done some internet research I found only a few DIY customized load balancers.

    Note this is a large legacy desktop application having dozens of components and hundreds of interface methods written in good old VC98/VB6/COM technology, therefore cannot easily redesign or use latest technology like .NET remoting, IIS, etc. - so the preferred solution is independent from the application.

    Any suggestion?

    Thanks, Tamas

    Wednesday, April 18, 2012 1:29 PM