Insights from the load balancer experts

I’m excited and slightly scared by our latest product! Excited because I've become slightly addicted to launching multiple instances in different parts of the world and load balancing the traffic seamlessly. Scared because this could change our whole business model...

The vast majority of layer 4 load balancers use LVS in two-arm NAT mode...

Here at Loadbalancer.org we have recently started the certification process of our product with Microsoft Office Communications Server (OCS)...

When you have users depending on Windows Terminal Services for their main desktop, it's a good idea to have more than one Terminal Server. RDP, however, is not an easy protocol to load balance...

I've previously blogged about how to get TPROXY and HAProxy working nicely together, but what if you want to terminate SSL traffic on the load balancer to use HAProxy to insert cookies in the standard HTTP stream to the backend servers?..

Some vendors make a fair bit of hype about their products enabling 99.999% availability out of the box...

If you use HAProxy as the load balancer then all of the backend servers see the traffic coming from the IP address of the load balancer...

Standard Kernel builds of LVS (Linux Virtual Server) don't have the ability to load balance traffic that is from the local node...

One of the (many) traditional problems with load balancing is the requirement to change your infrastructure in order to implement a hardware load balancer...

Direct Routing aka. Direct Server Return (DSR) aka. N-Path is a great load balancing method. And it is, without doubt, the fastest method possible...

Hardware marketing execs get very excited about the fact that their product can magically scale your application by using ‘amazing Layer 7 technology’ in the load balancer such as cookie inserts and tracking/re-writing...