![Active/active for N+1 redundancy from Loadbalancer](/blog/content/images/size/w1000/2024/06/two-generic-red-racing-cars-with-same-livery-driving-at-high-speed-along-a-straight-section-of-racetrack-under-bright-blue-dawn-sky-with-some-white-clouds-purplified-700x400-tiny.png)
![Joshua Turnbull](https://www.loadbalancer.org/blog/content/images/2022/09/josh-pic-edit--B-W-.png)
Active/active for N+1 redundancy from Loadbalancer
I've been repeatedly asked how our load balancers scale. So, I have decided to write down your options for endlessly scalable, high-performance load balancing.
I've been repeatedly asked how our load balancers scale. So, I have decided to write down your options for endlessly scalable, high-performance load balancing.
For the uninitiated, Direct Server Return is a clever trick which entails directly routing packets to the chosen real server.
The plan is to use an inexpensive pair of load balancers - using Layer 4 DR mode for maximum throughput and transparency - to load balance some more mid to high-end load balancers. This enables us to handle the SSL offload at a much more affordable price than simply buying a big box.
To design a well-targeted disaster recovery plan, you need to work out two key metrics: the Recovery Point Objective (RPO) and the Recovery Time Objective (RTO).
The Loadbalancer.org appliance automatically detects changes in your auto-scaling groups, with zero configuration and zero downtime.
Yes, it's the end of an era... after many years arguing that GSLB has no place on a proper load balancer, I've finally found a solid reason to add one to our product. Yes, you read that right! I've officially surrendered and given you a new GSLB to play with...!
L3 DSR is an alternative technique to achieve direct server return at Layer 3. Instead of using an IPIP tunnel like LVS-TUN it changes the destination IP address like LVS-NAT when sending the traffic to the real server.
LVS-DR and LVS-TUN are both forms of Direct Server Return where the load balancer only has to deal with one half of the connection.
Whether archiving, editing or streaming media, downtime is not an option for the broadcast industry.
We decided that we would like to be able to change server states and bring them online, offline or drain them. So asking Alexa to do this would look like “Alexa ask Val to change status of website1 to drain”. So we started work with this as our goal.
During the major IT project to consolidate domains, the use of virtual Loadbalancer.org solutions on a temporary basis helped BenQ to ensure business continuity.
Updates include an enhanced process for high availability appliance pairing, improved LBCLI, and advancement of the web user interface.
Some of the most common questions we get at Loadbalancer.org are performance related. It is quite difficult to give a straight answer to these questions as the real answer is often slightly unsatisfactory.
I must confess, at certain times it has looked like open warfare would break out between the support team and development team at Loadbalancer.org over the last few months.
A couple of customers asked if our appliances would do G-Zip compression. In the past we hadn't given it much thought until someone offered us a card to test it!
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.
One of the (many) traditional problems with load balancing is the requirement to change your infrastructure in order to implement a hardware load balancer.
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.