Loadbalancer.org Reviews

The primary use case of this solution is for the web application firewall. We have a Metaswitch system for our telephone service. We're front our SIP provisioning servers and our client communications portals with the WAF.

Loadbalancer.org together with Metaswitch in Enfield, England wrote a set of rules that are being managed on the Loadbalancer to prevent illegal entry, password hacking attempts, invalid SIP provisioning hacking attempts, or just general denial of service attacks into our cloud. It ensures that only what we expect to hit our systems is let through.

The solution has improved our organization by providing the security required to block break-in attempts easily and without overloading the WAF or getting to our servers.

We use Loadbalancer.org to check Nova Network and also use it for F5. We use its load-balancing technology.

I found scalability in Loadbalancer.org valuable.

In our experience, Loadbalancer.org is best suited for small businesses looking to balance their website. They don't require HA, DR, or anything else.

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.

Our primary use case for Loadbalancer.org is on the presale point for clients who use the solution for balancing loads.

The most valuable features of Loadbalancer.org are related to its load balancing capabilities.

We load balance our customer billing and information system, as well as our Exchange services with it.

We had a requirement for these applications to be load balanced. Without a dedicated load balancer, we would have had to use a Round Robin DNS, which does not have any health checking, notifications, etc. We now get notifications when pool members go down, and we eliminate our downtime by not sending traffic to downed pool members.

I work for a value-added reseller.

Loadbalancer.org is used when an application has multiple instances. 

There are also cases where you have a production and a disaster recovery scenario, and the customer wants the users to be able to switch from the production servers to the disaster recovery servers with as little downtime as possible.

The performance is good.

We use this solution when publishing Windows based applications and other custom based SQL applications. We are in the progress of migrating the on-premises data center to the cloud and continue to use Loadbalancer for this.

Loadbalancer has improved our organization. When we enable load balance between the two servers and we experience an issue in trying to connect to a specific URL, we can reduce the impact using this solution. One of the servers will be supporting the users so there will be no downtime and no impact on productivity. This is one of the main reasons that we use Loadbalancer.

Load-balancing a web application server. It's a requirement for the application which we're using, which is why we bought the hardware. It does its job. We don't touch it.

We couldn't use our line-of-business software without it. It sits in front of it and it just does its job. It's an unsung hero, I'm afraid. It just does what it does. It plods along everyday, and when it breaks, it gets fixed really quickly.