Cloud-first deployment is the choice of many organizations when they are looking to roll out new applications and services, or when they come to upgrade existing ones. The benefits of Cloud deployment are well known and don’t need repeating here.
In many scenarios, deploying in the Cloud does not remove the need to have multiple virtual servers to deliver applications and services. If anything, deployment in the Cloud means that the potential user base will be larger than when applications were hosted on private infrastructure. This means that the need to intelligently spread the user load across application server instances has not gone away.
Load balancers are the way to make sure that incoming access requests are allocated to a server that is capable of optimally handling them. Deploying to the Cloud does not mean that load balancers are obsolete. This is evidenced by the fact that the major public Cloud providers make cloud-based load balancing services available. Amazon provides AWS Elastic Load Balancing, and Microsoft provides Azure Load Balancer.
Cloud provider load balancers are basic offerings that do not provide the power and flexibility required for modern application architectures and deployment models. Kemp LoadMaster is Cloud-native and is a much better option. It is both more powerful, and it works out to be cheaper than the native offerings.
In this post, I’ll take a look at the AWS load balancing options and compare them to LoadMaster. If you’d like a similar comparison to Microsoft’s Azure Load Balancer, then reach out and let me know.
AWS has three load balancer options. Two are current, and one that is only supported on legacy infrastructure. The three AWS options are:
Kemp LoadMaster is available within the public Cloud providers Marketplace stores, and it is also available as a Virtual LoadMaster (VLM) for use if you are building a Cloud based infrastructure using assets outside of the Marketplace options. For completeness, I’ll also mention that hardware device versions of LoadMaster are available for rack mounting if your deployment model requires that. Some of the hardware devices have dedicated SSL/TLS processing components to speed up encryption processing in SSL/TLS offloading scenarios.
Using LoadMaster in the Cloud in preference to the AWS (and Azure) native load balancers brings many benefits. For example:
The tables below show the costs for both kinds of AWS load balancers, and also for deploying LoadMaster in AWS. The cost savings are stark. With LoadMaster you get a better load balancer at a fraction of the cost.
The AWS Layer 4 load balancer costs:
The AWS Layer 7 load balancer costs:
The costs for the AWS load balancers start high and then get astronomical! LoadMaster pricing tells a different story:
What? Where’s the catch? There isn’t one. With LoadMaster you get a more feature-rich and powerful load balancer, with a dedicated human support team, at a fraction of the cost.
If you want to try LoadMaster for yourself, then visit the dedicated free trial site.
If you want to talk to someone in Kemp about LoadMaster or our other solutions, then visit our Contact Us site.