A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Verified User
Administrator in Information Technology (51-200 employees)
Use Cases and Deployment Scope
Kemp LoadMaster is used as a load balancer by all the users and for all web applications.
Pros
Easy to use. The interface is intuitive and there is no need to be Kemp expert to setup a new VIP or to make changes in the existing configuration.
Unlike some other products, all options and buttons are present here in the same page. Once you quit the page, either you did it well and it works or it does not work and you did not do it well.
Except for special rules, no need to configure groups or permissions or whatever in deep hidden pages before setting up your VIP. All you need is present in the same interface. Just click and select, that's all. The settings are auto applied.
Reactive support. The Kemp support team answers fast with revelant information.
The support knows that your time is important and does not ask for useless information. They don't ask for the 10 past years logs or what you have eaten last day ([questions with] no link to your issue, you probably got such weird questions with some other vendors )
No weird issues.
As far as I know, the Kemp LoadMaster does not create major issue for "bugs" or for any other reason. The appliances are stable.
Cons
I don't know. For the basic needs I have, the Kemp LoadMaster is enough. But as said, my needs are basic (creating VIP for load balancing http/https sessions, and sometimes redirecting webpages ). So maybe this appliance misses features but I don't need them at the moment.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Verified User
Manager in Information Technology (501-1000 employees)
Use Cases and Deployment Scope
We use this to load balance internal services for our users. We have a few services that we have using this and it is easy to use and configure
Pros
Load balancing
Configuration
Logs are easy to read through
Cons
A better interface
easier to use logs
easier HA configuration
Return on Investment
Low cost solution
easy to implement and maintain
Provides HA uptime of the required internal services
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
IT Specialist in Information Technology at Myron Corp (1001-5000 employees)
Use Cases and Deployment Scope
Our company has used Kemp LoadMasters for several years now for load balancing our Exchange servers and a couple of web applications. They run very smoothly, with no issues at all. Their support is great, which we only occasionally have recurred to for migrating web apps from other appliances to the Kemps. They are very knowledgeable and have been very helpful in completing our project goals. Would definitely recommend Kemp products.
Pros
Load balancing
Reliability
Robust support
Cons
GUI could use some improvement
Return on Investment
Has helped us maintain services up and running, no matter the load.
Distributes loads among servers, so no one server is overloaded.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Systems Engineer in Information Technology at Doherty Associates (51-200 employees)
Use Cases and Deployment Scope
Kemp LoadMaster is generally used for our clients and internally. This is to help load balance Exchange HTTP and HTTPS traffic coming into the Exchange server. We also widely use this to have SMTP and SMTPS traffic load balanced as well. This way we have managed to control the kind of high load that is hitting the exchange server and have it at a much more managed level, routing it through Kemp LoadMaster.
Pros
It is easy to set up the virtual services with templates that are readily available.
Once the setup of the virtual services is complete, getting the service to work is also, most of the time, pretty seamless.
When all else fails and doesn't work, the support team is usually just a call away, and I've almost always had a good experience calling them for support.
Cons
The wait time on the calls can sometimes be quite disappointing. I have waited on calls for over 30 minutes in the past before an agent answers the call.
For some weird reason, every time a support agent starts a remote session, our call gets disconnected. And it can sometimes be a bit of a pain to call back and speak to the same agent, as sometimes we haven't been given a ticket number as well and will have to explain the issue over again to the new agent who picks up the call. This issue happened on this call as well. Maybe it'd be good to provide ticket numbers at the start of the call?
Maybe it is the type of microphones the agents use or because everyone is working at home currently (mostly), but the voice clarity of the call could be improved, as sometimes its difficult to hear what the agent is saying.
Return on Investment
We have little worry of our load balancing traffic, as it is almost mostly reliable and even in the event of a failure, the secondary usually kicks in so we barely notice any downtime.
Our customers love the idea of having a reliable load balancer and one of our biggest clients has also recently agreed to roll out Kemp LoadMaster on all their sites, which is great news for us as a company.
Usability
Alternatives Considered
Azure Load Balancer, Symantec Cloud Workload Protection and Azure Kubernetes Service (AKS)