We're working on a project where our customers use HJ. We utilize their load balancer to evenly distribute the data load between multiple servers, ensuring that one server doesn't become overloaded.
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.
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.
Senior Network and Security Specialist at a tech services company with 51-200 employees
Real User
Top 20
2022-07-06T15:05:15Z
Jul 6, 2022
It has different models doing different things. One is basic load balancing. The other is doing a web application firewall. Another use case is for handling VPN exposure resources. There is one doing advanced DNS sharing as well.
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.
IT manager at a university with 1,001-5,000 employees
Real User
2020-12-03T15:07:14Z
Dec 3, 2020
We are using this solution for internet management. We have approximately eight incoming ISP lines. All of the ISP lines go to the load balancer. We use it for normal internet access.
IT Manager at a recruiting/HR firm with 51-200 employees
Real User
2018-02-28T07:44:00Z
Feb 28, 2018
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.
Loadbalancer.org is a versatile solution that offers load balancing for small businesses, multiple instances of applications, web application firewall, publishing Windows and SQL applications, and security for telephone service systems. It is easy to use, cost-effective, and performs well with low latency.
The connection maintenance and security features are valuable, including managing logs on WAFs, identifying break-in attempts writing rules to block them and using HAProxy to control...
Our primary use case for Loadbalancer.org is on the presale point for clients who use the solution for balancing loads.
We're working on a project where our customers use HJ. We utilize their load balancer to evenly distribute the data load between multiple servers, ensuring that one server doesn't become overloaded.
We use loadbalancer to provide availability for almost every essential application
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.
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.
It has different models doing different things. One is basic load balancing. The other is doing a web application firewall. Another use case is for handling VPN exposure resources. There is one doing advanced DNS sharing as well.
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.
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.
We are using this solution for internet management. We have approximately eight incoming ISP lines. All of the ISP lines go to the load balancer. We use it for normal internet access.
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.