In this ever-increasing application economy, IT administrators and cloud architects are constantly looking at simpler and more efficient ways to:
Gain Application Performance Visibility
Stop Blame Game among Network, Server & Developer Teams
Empower App Developers to Deploy Apps in Minutes
Manage and maintain Load balancing services with minimum effort
Why Load Balancing Matters for Customers
We live in Application economy.
Delivering great application experience is synonyms with business growth, better customer satisfaction and workforce productivity.
Load Balancing enables better application experience.
Load Balancing is fundamental building block of cloud as Compute, Storage & Network
One can not realize the value of applications and digital transformation without load balancing.
VMware customers value NSX-ALB integration with their existing VMware software stake.
Avi Networks platform, now known as VMware NSX Advanced Load Balancer is a modern – software defined – elastic – application delivery fabric. It is composed of a central control plane and a distributed data plane.
Avi Controllers provide a centralized policy engine which delivers full life-cycle management for applications
Avi Service Engines are the load-balancers which can be deployed anywhere, natively in a fully orchestrated fashion by the Avi Controllers, On-premise or in the public-clouds.
Avi Controller consumes application intent via REST APIs and strives to realize that intent. As an example Avi Controller would
- Creates Avi SEs
- Acquires IP for VIP through IPAM
- Registers FQDN to DNS
- Manages application certificates
- and so on ...
All the user ever needs to do is to simply convey the intent
Eliminates the problems of overprovisioning and overspending by scaling load balancers elastically based on real-time traffic.
Provides a self-healing fabric. If an Avi SE fails, applications are dynamically moved to other available Avi SEs ensuring that the required capacity for applications is always available and also creates new Avi SEs to replace the failed Avi SE.
Provides a single point of control and multi-cloud support: This enables a universal solution for traditional, modern, and cloud-native use cases across all environments. Applications can reside on any-cloud and Avi Controllers would provide the same level of automation regardless of where the application is provisioned.
Provides rich performance monitoring and visibility into client, security, and application insights that simplifies troubleshooting and automates decisions.
High latency & performance issues:
Latency & performance
No native LB offering, try to use on-prem LB for VMC
Web-app-DB architecture requires hair-pinning (on-prem LB)
If using F5 VE (performance limitation)
If using VPC, hair-pinning between AWS & SDDC
Sub-optimal traffic flows:
Traffic trombones between ELB and VMC through compute gateway
Huge increase in latency
Unreliable support & lack of certification:
Support & certification
Some apps are not rewritten (goes on VMC not AWS)
Preserving client IP (HTTP header)
Asymmetric routing (not a custom default gateway)
Not a supported typology eg. default gateway (one-off approval)
VDD – certified
.
Software upgrades
Health monitoring
Backups and handling DR
Faster troubleshooting by SRE team
Anomalous Behavior
Misconfiguration
Sizing and Scaling requirements
SDDCs are placed on regionally co-located controller based on capacity
Regional Controller Cluster per Customer - Hosts multiple SDDCs
- Each SDDC is a tenant
GA - Shared controller cluster. Customer + SDDC mapping to a tenant
CSP is used for authentication and billing
Firstly, it is anchored by a common data platform that we introduced with Aria Hub and Graph and we’re working to extend across the Tanzu platform. This allows you to see how an app is performing on the development side and how does that differ from production, see the security characteristics and how these change as an app moves down the pipeline? But a common platform doesn’t mean that it’s just our platform – this is a common platform that is open and built on open source, cloud native technologies so that you can plug in existing tools.
Software upgrades
Health monitoring
Backups and handling DR
Faster troubleshooting by SRE team
Anomalous Behavior
Misconfiguration
Sizing and Scaling requirements