Your Avi alternative, without the renewal shock
Your Avi renewal quote has stopped looking like a renewal. This session is about what comes next: how to move application delivery off Avi without rebuilding from scratch, and what changes for the operators who run it. We're honest about where the migration gets tricky.
Broadcom's acquisition of VMware changed how Avi Load Balancer is licensed. Perpetual licensing is gone, so subscription is the only path. Avi is also licensed separately as a VMware Cloud Foundation advanced service, not as part of the core platform. The licensing change reaches into operations, too. Activation now runs through Broadcom, so an Avi deployment is no longer fully self-contained. Moving to HAProxy keeps that activation on your own infrastructure, under your control.
Avi separates control from data. Controllers manage configuration while Service Engines carry traffic. HAProxy maps that onto HAProxy Fusion for centralized control and HAProxy Enterprise for the data plane, with HAProxy ALOHA appliances for teams that want to keep hardware on the rack. Global server load balancing (GSLB) routes traffic across regions.
What we'll cover:
How the Avi Controller and Service Engine split maps onto HAProxy Fusion and HAProxy Enterprise.
Where Virtual Services, Pools, and DataScripts land in a haproxy.cfg, and what the conversion looks like.
A cutover sequence that runs both stacks side by side, and which services to move first.
Four deployment patterns: VRRP pairs, Anycast, multi-region GSLB, and Kubernetes.
How to replace rather than upgrade, adding nodes and shifting traffic without a maintenance window.
This one is for platform engineers, network architects, and infrastructure leads running Avi today, along with the IT leaders signing off on the next renewal. If you're weighing your options before the next licensing bill arrives, you'll leave with a concrete migration path and a clear view of what changes for your operators.
Speakers
