Submitted March 23, 2021
Author: Avinash Kumar
The agility and flexibility cloud provides are critical to helping customers meet their business needs, and most adopt a hybrid-cloud or multi-cloud approach. That said, cloud is not free, and the increase in cloud adoption has put more focus on the total cost of operations and how to lower it. After all, the application infrastructure cost is one of the major components of IT expenses.
A prime example of how NetScaler ADC helps many customers to reduce back-end infrastructure cost is through connection multiplexing. This blog post will highlight three ways NetScaler ADC can help you save money on your cloud journey:
- Use of NetScaler ADC instead of L4 load balancers that don’t support multiplexing on cloud
- Consolidation of L4 and L7 load balancing and application security in the same NetScaler ADC for better management and visibility
- Complement cloud load balancers (for example, using NetScaler ADC behind L4 cloud load balancers)
In each case NetScaler ADC can reduce back-end infrastructure costs via connection multiplexing, resulting in the use of fewer servers.
What is Connection Multiplexing?
Connection multiplexing is a method of reusing connections to avoid the overhead on the server that comes with establishing new connections for each request. Connection multiplexing support in NetScaler ADC ensures that server connections are efficiently reused, which results in dramatically reduced SSL/TLS load on back-end servers.
Solution 1: Use of NetScaler ADC instead of L4 load balancers that don’t support multiplexing on cloud
For any given load, the use of NetScaler ADC requires 40 percent fewer back-end servers when compared with L4 load balancers in the cloud. This is because NetScaler ADC supports connection multiplexing. L4 cloud provider load balancers without multiplexing support must establish a new connection for each request, which places more compute burden on the back-end servers, especially for TCP and SSL/TLS.
For Example, a L4 load balancer without multiplexing support might require five back-end servers to cope with a load of 5,000 SSL connections per second. With NetScaler ADC, three servers would suffice. NetScaler ADC reuses connections, which reduces the processing overhead on each server by around 40 percent, as shown below.
Load Balancer | Backend Servers (AWS C5.large – $0.085/hr) | Monthly Server Cost ($) (~40% saving with NetScaler ADC) |
L4 load balancer without multiplexing support in cloud | 5*0.085 = $0.425/hr | 306 |
NetScaler ADC | 3*0.085 = $0.255/hr | 184 ($122/Month Savings for 5K SSL TPS) |
Table 1: The difference in overall cost for compute resources to handle the given load on AWS Cloud
Load Balancer | Backend Servers (Azure A2V2 – $0.076/hr) | Monthly Server Cost ($) (~40% saving with NetScaler ADC) |
L4 load balancer without multiplexing support in cloud | 5*0.076 = $0.38/hr | 273.6 |
NetScaler ADC | 3*0.076 = $0.228/hr | 164.2 ($109.4/Month Savings for 5K SSL TPS) |
Table 2: The difference in overall cost for compute resources to handle the given load on Azure Cloud
The resulting savings here is $122 per month in AWS and $109.4 per month in Azure. In other scenarios, these savings can be much higher as customers use more servers to cope with larger workloads. In all the scenarios, you will see a cost savings of about 40 percent in server computing because of NetScaler ADC and multiplexing support.
Solution 2: Consolidation of L4 and L7 load balancing and application security in the same NetScaler ADC for better management and visibility
In many cloud deployments, customers use two different layers of load balancers for Layer 4 and Layer 7 decision-making. The consolidation of distinct L4 and L7 load balancers into a single NetScaler ADC provides three distinct advantages
- 40 percent savings on back-end infrastructure via multiplexing
- Lower operational overhead (consolidation of multiple service types — HTTPS, TLS/SSL-TCP, HTTP, TCP, UDP)
- Lower total cost of ownership — NetScaler ADC supports both Layer 4 and Layer 7 Service types
In addition, the enhanced feature set of NetScaler ADC reduces the need for additional services like a web application firewall for application security, reducing costs further.
Solution 3: Complement cloud load balancers (for example, using NetScaler ADC behind L4 Cloud load balancers)
Some customers want to retain Cloud load balancers and use NetScaler ADC, as shown below, to save on server workloads. There are a variety of reasons for this, including:
- Retain the L4 cloud load balancer as Tier-1 load balancer to maintain a single static IP address per availability zone
- Use NetScaler ADC as a Tier-2 load balancer to reduce server cost by 40 percent
- Use NetScaler ADC for its rich Layer 7 functionalities like global server load balancing (GSLB), rewrite, responder, authentication, and application security (WAF) use cases.
With NetScaler ADC, you can lower server TCO by 40 percent, lower your operational overhead by consolidating multiple service types (HTTPS, TLS/SSL-TCP, HTTP, TCP, UDP) in a single NetScaler ADC, and complement your Layer 4 cloud load balancer. Learn more about NetScaler ADC today.
Recommended Comments
There are no comments to display.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now