Flexible Load Balancing automatically distributes incoming traffic across multiple targets – Nobus FCS instances, containers, IP addresses, and functions – in multiple Availability Zones and ensures only healthy targets receive traffic. Flexible Load Balancing can also load balance across a Region, routing traffic to healthy targets in different Availability Zones. The Nobus Flexible Load Balancing Service Level Agreement commitment is 99.99% availability for a load balancer.
Secure
Flexible Load Balancing works with Nobus Private Cloud (private cloud) to features, including integrated certificate management, user-authentication, and SSL/TLS decryption. Together, they give you the flexibility to centrally manage TLS settings and offload CPU intensive workloads from your applications.
Flexible
Flexible Load Balancing is capable of handling rapid changes in network traffic patterns.
Additionally, deep integration with Auto Scaling ensures sufficient application capacity
to meet varying levels of application load without requiring manual intervention.
Flexible Load Balancing also enables you to use IP addresses to route requests to application targets.
Robust monitoring & auditing
Flexible Load Balancing gives you to monitor your applications and their performance in real time with logging, and request tracing. This helps visibility into the behavior of your applications, uncovering issues and identifying performance bottlenecks in your application stack at the granularity of an individual request.
Flexible load balancing
Flexible Load Balancing allows ability to load balance across Nobus and on-premises resources using the same load balancer. This makes it easy for you to migrate, burst, or failover on-premises applications to the cloud.
Use cases
Achieve better fault tolerance for your applications
Flexible Load Balancing provides fault tolerance for your applications by automatically balancing traffic across targets
– Nobus FCS instances, containers, IP addresses, and functions –
while ensuring only healthy targets receive traffic.
Automatically load balance your stacked applications
With enhanced stack support for Flexible Load Balancing, you can now load balance across multiple ports
on the same Nobus FCS instance.
Automatically scale your applications
Flexible Load Balancing provides confidence that your applications will scale to the demands of your customers.
With the ability to trigger Auto Scaling for your Nobus FCS instance fleet when latency of any one of your
FCS instances exceeds a preconfigured threshold, your applications will always be ready to serve the next customer request.
Using Flexible Load Balancing in your Nobus Private Cloud (Nobus private cloud)
Flexible Load Balancing makes it easy to create an internet-facing entry point into your
private cloud or to route request traffic between tiers of your application within your private cloud.
You can assign security groups to your load balancer to control which ports are open to a list of allowed sources.
Because Flexible Load Balancing is integrated with your private cloud, all of your existing Security Group and Routing
Tables continue to provide additional network controls.
When you create a load balancer in your private cloud, you can specify whether the load balancer
is internet-facing (default) or internal. If you select internal, you do not need to have an internet
gateway to reach the load balancer, and the private IP addresses of the load balancer will be used in
the load balancer’s DNS record.
Flexible load balancing
Flexible Load Balancing offers ability to load balance across Nobus and on-premises resources using the same load balancer.
You can also use Flexible load balancing to benefit separate applications where one is in a private cloud
and the other is in an on-premises location.
Simply put the private cloud targets in one target group and the on-premises targets in another target group,
and then use content based routing to route traffic to each target group.
Invoking functions over HTTP(S)
Flexible Load Balancing allows method invoking to handle requests from HTTP(S).
It enables users to access serverless applications from any HTTP client, including web browsers.
You can register functions as targets and leverage the support for content-based routing rules in
Application Load Balancers to route requests to different functions.