The features I find valuable in this solution are the ease of managing the logs on the WAFs, the ease to identify break-in attempts into the network, writing rules to block them for files or config pull attempts, and the addition of HAProxy to control what is allowed and what is not.

I found scalability in Loadbalancer.org valuable.

Loadbalancer.org is less complex than Citrix. In some cases, our customers do not have an engineer on staff who can support this device.

These customers have a large number of Linux engineers but don't have the money. We suggested using Loadbalancer.org and other open-source tools. Many customers are of different sizes and have different budgets.

Loadbalancer.org has everything that is needed.

The connection that this solution helps our servers maintain has been most useful. 

The performance is good.

If all the data traffic is directed to a single server, it can become overwhelmed. Load balancing helps us distribute both incoming and outgoing data loads evenly among the servers, preventing overload on a single server.

The SSL Layer 7 load balancing.

A load balancer is a load balancer, in terms of functionality. I need the interface to be easy to use for my team members who have not spent hours working on it, so I am not the only person who can operate it.

The most important feature is the fact it was recommended by the supplier. The previous load balancers weren't a very good match for what we were trying to do.

They work. It just keeps going. The vendor will set them up, and they've just been trouble-free. They've just worked. They just keep going. That's what the principal purpose of the load balancer is, to work around and be available when there's any outages with the cluster behind. They just keep going, which is exactly what we want them for.

Existing customers are trying to migrate from the physical F5 load balancer to the AVI load balancer because it is scalable and easily managed. The solution's analytics is also very good.

Ease of use and support.

The user interface precludes need to be well versed with Linux IPVS command line. This make it easy for junior team members to participate in managing load balancing needs. 

The support especially helps us with quick remote fixes. With a remote fix, I can view the fix in real time and yet ease security concerns for my supervisor. We had a few issues and they responded immediately. They came in remotely and fixed them. Everything is really good from the customer service point of view, which is what we expected it to be.

• Reliability 
• High availability

Most important for us that it makes sure that the load is distributed and that we always have access to the end-servers that they're connected to. We need that to make sure that we have a consistent, high level of service that the schools can rely on.

First of all it's the reliability, what you create by load balancing, because you have more endpoints. That's for our web services that we provide. This is the only feature for us, and it's important because it makes our network more reliable.

F5 is a balancer that is one of the first to do this kind of thing, so it's pretty much a Swiss Army knife for managing all the load balancing techniques. It's pretty much complete in terms of the offering.

Loadbalancer is easy to use. It performs well, with low latency. 

It helps us to route the traffic to the available servers. If we didn't have Loadbalancer we would fail to set the end-user and it would cause a failure in the cluster. We protect the cluster with Loadbalancer. It checks all of the nodes in the backend, in the fabric. If you enable the monitor it will set an alarm in the server. When a user gets an application, this alarm alerts the user.

SSL Termination with Server Name Indicator option to a Layer 7 back end web farm which allows the client IP address to still be passed.

The load balancers have an easy installation and a relatively simple, easy user interface to use, which is valuable because it is not the core business of our engineers to configure network devices. With basic network knowledge, our required system functionality can be configured and maintained.