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, the front-end firewall, and a more specific firewall.
We can more easily set up a test environment, because you can easily configure your forms. It makes it more flexible for us, to convert our test environment to a production environment, without having to change DNSs on the outside. You just configure the forms on the inside. So without changing the actual endpoint for the end user, we can create completely different networks in the background.
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.
You can run into an issue when one engineer passes the case over to another engineer after their shift and they don't know what the first engineer worked on up to that point.
Senior ICT Support Officer at a government with 5,001-10,000 employees
Mar 5, 2018
They're mostly designed to balance a particular type of traffic. I wanted to load balance DNS, and they just don't do it the way that we wanted to. So they're not used as DNS load balancers.
It would be great if there was a way to gain access to the graphing data, to create custom reports. If we had a way to use the graphing data, we could use it to present certain information to our client, such as the uptime status for their service.
Systems Programmer at a energy/utilities company with 501-1,000 employees
Mar 14, 2018
I would like a notification when a new version of the software is available. They told me to sign up for their newsletter, but I have not received any notification for a newer software version.
An area for improvement in Loadbalancer.org is that sometimes it works fine, but sometimes, it has issues. The setup for Loadbalancer.org is also complex, so that's another area for improvement.
