There are many load balancing/ ADC vendors on the market so how do you go about comparing them? What one is best?
The answer as you might expect is not simple and very much depends on your circumstances and requirements. To try and simplify things we will discuss in terms of the categories below that will make comparing load balancers slightly easier.
We still talk a lot about βload balancingβ or load balancers but really these devices have evolved significantly and do a lot more than just load balancing. This is the reason why Gartner coined the new term ADC β Application Delivery Controller.
When comparing load balancer we will compare them with respect to ADC functionality as they will all do a great job of basic layer 4 load balancing and its really itβs dying requirement.
It worth noting that some vendors have an βapp storeβ that will allow you to download new functionality and /or apps onto the device.
This is useful especially for software ADC. Unlike a Hardware load balancer a software load balancer can be consistently upgraded and as such has no inherent βshelf lifeβ that dictates at some point it will require a complete load balancer hardware refresh.
These devices have evolved form a complex geeky networking world where you would only be able to configure them after a 2 week course with command line whilst tapping out binary.
The modern usability assessment is more like this:
Usefulness Factor = (Amount of Features Available + Usability) /
(Amount/Time/Cost of Training Required)
For many people managing the ADC is just a small part of their work and as such cant commit the time for drawn out training.
This really ties back into the functionality. Some of the top end devices have all the functionality but the educational investment is so great that itβs wasted.
Whilst this may be ok for the Enterprise where they have the βload balancer/ADCβ person it might not work for the mid market where they still may have complex requirements but not necessarily so much dedicated time
So the lesson here is ensure the vendors you are looking at have the feature you require but also ensure its packaged in a useable way.
Many years ago when load balancers were basic layer 4 devices and the next generation of layer 7 ADC devices was emerging this was a massive concern. Layer 7 devices can now deliver outstanding performance.
Many load balancers use the same open source LVS/HAproxy etc code as such they all have a similar performance profile.
This understanding means that they can add value to the transaction from SSL, Caching to more complex traffic management modifying the request and response. Depending on how many of these features you enable you will use significantly more or less CPU.β
So most vendors will have a device/software that will cope with your capacity its just choosing the right model. Some will offer a βsizingβ tool but these are typically inaccurate as they dont consider the use case. You are much better off having a quick call with the vendor to be sure.
If you are building the next version of google then you should consider vendors such as f5 networks as they have the most scalable solutions else most load balancing vendors offer pretty good performance way more than 99.999 could ever use. Ie Edgenexus can do 40Gbs+ at layer 7.
It is worth noting that most most vendors donβt publish any performance metrics with layer 7 rules in use as these will have a massive effect on performance. It is common that when load balancing a web application some rules such as URL redirect will be used.
So there is Price and Value.
Typically there are 4 components:
However something else that should be considered is flexibility of the licensing.
You may be purchasing these for 3-5 years as such you may be moving from hardware to software or software to cloud. How can the vendor support this? For example can they offer a free licence migration from hard to software?
|
Name
|
Function
|
Usability
|
Performance
|
Value
|
Total
|
|---|---|---|---|---|---|
|
Edgenexus ADC-X
|
ππππ
|
πππππ
|
ππππ
|
πππππ
|
18
|
|
f5
|
πππππ
|
πππ
|
πππππ
|
ππ
|
15
|
|
A10
|
ππππ
|
ππ
|
ππππ
|
ππ
|
12
|
|
Citrix Netscaler
|
ππππ
|
πππ
|
ππππ
|
πππ
|
14
|