State of Load Balancing 2020
•Download as PPTX, PDF•
1 like•238 views
Watch webinar on-demand here https://info.avinetworks.com/webinars/state-of-load-balancing-2020 2019 has been an eventful year for load balancing. Avi Networks is acquired by VMware, who enters the application delivery controller (ADC) market with a software load balancer, web application firewall and container ingress solution. NGINX is acquired by F5 Networks, hoping to tap into the developer communities. We continue to see the rise of multi-cloud and microservices as the leading drivers behind changes in modern load balancing solutions. In this webinar, we will explore three technology areas: - A new perspective on “service chain” – how it helps integrate adjacent technologies with APIs to form a self-service portal - Implications of HTTP3 on the future – why it is interesting to the load balancing industry in particular - An early prediction on DNS over HTTPS (DoH) – why it can enhance the security, scale and resiliency of the internet
Recommended
More Related Content
What's hot
What's hot (20)
Similar to State of Load Balancing 2020
Similar to State of Load Balancing 2020 (20)
More from Avi Networks
More from Avi Networks (6)
Recently uploaded
Recently uploaded (20)
State of Load Balancing 2020
- 1. ©2020 VMware, Inc. The State of Load Balancing Nathan McMahon nathanmcmahon@vmware.com
- 2. ©2020 VMware, Inc. Agenda 2 What Happened Predict the Future Align to the Future
- 3. ©2020 VMware, Inc. 3 Enterprises have almost 5 clouds Running 3.4 clouds Experimenting 1.5 clouds 84%HAVE MULTI-CLOUD STRATEGY * RightScale 2019 Cloud Report State of Load Balancing: Multi-Cloud
- 4. ©2020 VMware, Inc. 4 VMware OpenStack Containers Public Cloud Bare Metal State of Load Balancing: Multi-Cloud Avi deployment distribution across cloud types GSLB Globally LB across clouds Manage Consistent LB config across clouds Automation Consistent API across clouds
- 5. ©2020 VMware, Inc. 5 Single request per TCP connection Headers are text Multiple requests per TCP connection, in serial Multiple concurrent TCP connections (usually 6) Headers are text Multiple requests per TCP connection, in parallel Currently about 43% of HTTP traffic is over HTTP/2, Usage up 30% year over year 6x reduction in concurrent connections on the load balancer Headers are binary HTTP 1.0 (1996) HTTP 1.1 (1999) HTTP/2 (2015) State of Load Balancing: RFC 7540 (HTTP/2) * W3Techs Report Jan 1st, 2020
- 6. ©2020 VMware, Inc. 6 What’s New: o TLS Fast Start o TCP Fast Open o New ciphers What’s Old: o Non-PFS ciphers o TLS 1.0 & TLS 1.1 State of Load Balancing: TLS 1.3 TCP SYN TLS Client Hello TLS Client Finished HTTPS GET TCP SYN ACK TLS Server Hello TLS Server Finished TCP SYN TLS Client Hello TLS Client Finished TCP SYN ACK TLS Server Hello TLS Server Finished HTTPS GET TLS 1.2 handshake TLS 1.3 handshake with Fast Start
- 7. ©2020 VMware, Inc. 7 What’s New: o TLS Fast Start o TCP Fast Open o New ciphers What’s Old: o Non-PFS ciphers o TLS 1.0 & TLS 1.1 State of Load Balancing: TLS 1.3 o Faster o More Secure o RSA keys are more vastly expensive o Elliptic Curve is in o NPM, taps, man-in-middle tools are blind
- 8. ©2020 VMware, Inc. 8 The market is changing quickly The hardware appliance vendors have explored selling Nginx sold Avi Networks is now part of VMware State of Load Balancing: Acquisitions
- 9. ©2020 VMware, Inc. 9 2019 has been an eventful year for LB & WAF VMware Enters the ADC market NETWORK AND SECURITY VIRTUALIZATION Security Integration Extensibility Automation Elasticity NSX Data Center NSX Cloud AppDefense SD-WAN by VeloCloud HCX NSX Service Mesh Advanced Load Balancer Avi Networks, now part of VMware
- 10. ©2020 VMware, Inc. Agenda 10 What Happened Predict the Future Align to the Future
- 11. ©2020 VMware, Inc. 11 Multiple parallel requests over a single TCP stream Vulnerable to head of line blocking HPACK Compression Multiple parallel requests streamed over a UDP / QUIC connection Packet loss and congestion don’t necessarily slow all request/responses QPACK Compression HTTP/2 HTTP/3 State of Load Balancing: HTTP/3 * W3Techs Report Jan 1st, 2020
- 12. ©2020 VMware, Inc. 12 The battle for the future of DNS is underway DNS over HTTP versus DNS over TLS Prediction: DoT will win over DoH over the next year State of Load Balancing: DNS
- 13. ©2020 VMware, Inc. 13 State of Load Balancing: Service Mesh Service chain will be supplanted by service mesh Service chain is typically narrowly defined as L2-L3 device interconnection Service mesh is the infrastructure to interconnect disparate services, most often microservices Prediction: Networking in 2020 will be the year of service mesh
- 14. ©2020 VMware, Inc. 14 State of Load Balancing: Service Mesh Ingress - Provides the cluster ingress data path capabilities - Security capabilities Side car - Provides the SM data path capabilities - Fully distributed Service mesh is the journey, not the destination
- 15. ©2020 VMware, Inc. 15 State of Load Balancing: Service Mesh VMware’s enterprise-class service mesh vision ServerlessSaaSVMsContainers Public Clouds Visibility Control Security Third-Party Components Users Services Data Customer Clusters VMware SaaS / Cloud Discovery Sidecars Sidecars / Federation Plugins Istio
- 16. ©2020 VMware, Inc. Agenda 16 What Happened Predict the Future Align to the Future
- 17. ©2020 VMware, Inc. 17 o Ease of useo Wall of knobs o Expect failureo 5x 9’s of uptime o Cattleo Pets o Integrationo Installation State of Load Balancing: Industry Trends
- 18. ©2020 VMware, Inc. 18 Creating a new virtual service INTELLIGENCEELASTICITY AUTOMATIONMULTI-CLOUDSEPARATE CONTROL & DATA PLANE WITHOUT AVI WITH AVI ? ? ? ? ? 1 6 3 4 5 2 7 8+ Done DECISION AUTOMATION Done 1 Declare VS attributes Minutes Weeks ? ? ? ? ? 1 6 3 4 5 2 7 8+ Sizing Procure HW Config LB Routing, FW policy LB Exists? Correct env? Capacity?Perf ? Dependencies? Config Auth Config Alerts Reserve IP Repeat for standby “I want to create a virtual service” 1. Checks existing capacity 2. Spins up new Avi Service Engine (if needed) by talking to vCenter/AWS/K8S/... etc. 3. Allocates VIP address 4. Configures network interfaces on Avi SE 5. Provisions policies on the Avi SE 6. Registers DNS 7. Monitors performance 8. Goes back to #1 and scales out as needed State of Load Balancing: Avi Automation
- 19. ©2020 VMware, Inc. 19 * 49% Think “Network Automation Software / Tools” is a top strategic initiative *Gartner Market Guide for Network Automation Poll State of Load Balancing: The Destination Automation o Self service portal o Intent based o Automated o Round robin, least conns o Service chain, service chain o REST API, Terraform o HTTP/2, HTTP/3, QUIC
- 20. Thank You ©2020 VMware, Inc. Want to know more? avinetworks.com/workshops Nathan McMahon nmcmahon@vmware.com
Editor's Notes
- Driving forces: Digital enterprises need to deliver more applications, faster, and at lower cost Consistent multi-cloud deployments across data centers and public clouds with enterprise level security Shift towards cloud-native apps and automation to support DevOps and CI/CD processes
- How Avi fits into the NSX portfolio but important to highlight: Continue to be offered as standalone LB for multi-cloud environments Plan to have the best integration with NSX and other VMWare products Transcription Avi Networks, now part of VMware, has been in business as a load balancer for about seven years (since 2012). We're now part of the VMware family as the NSX advanced load balancer. And VMware has been steadily introducing more and more networking functionality via NSX and other applications services and other functionalities. And Avi fits really nicely into that by providing the application delivery, the load balancing and application security such as web application, firewall, et cetera.
- 5. Automation – again it’s more than REST APIs and Ecosystem integration. Avi takes the analytics and feed into the controller (”brain”) to achieve autoscaling and full lifecycle management. It allows you to specify an intent, Avi does the automation and orchestration required to achieve the outcomes. What makes automation increasingly important is that it’s the critical step to finally operationalize digital transformation – from vision to reality. Transcription So by taking that information, that's really important to be able to provide troubleshooting and meaningful experience there. But it's also important because we can now take that data and use it for the purposes of automation. For automation, there's two elements to this. One is the operational automation. The other is the infrastructure automation. So from an infrastructure, that means that the Avi controller can natively be talking to the APIs of V Center, of Azure, AWS, you name it, in whatever the environment might be, the Avi controller is talking to those environments, to those controllers. So if you wish to deploy a load balancer or a service engine in a VMware environment, the Avi controller will talk to V Center, find the best location, the best host to deploy a new se.ova, and will automatically deploy that, configure the Nicks, et cetera, and take care of all of that for you. All you said is, "I want to upload or I want to deploy this application into VMware environment". So you're deploying the application or the purchase service that serve ascensions can automatically instantiate and automatically configure themselves for you. And so from an application owner perspective, here's my application, just make it go and the networking just automatically instantiates with it. The next element to this is the operational automation, and that is that Avi is not an island of technology in and of itself. It needs to be integrated with the surrounding environments, the surrounding ecosystems. Certainly that means something like V Center or Kubernetes or whatever environments like this, but it also means something maybe even more custom. It could be something like automatically configuring the IP addressing by talking to Infoblox or another IPN. We can automatically register virtual services into DNS by talking to something like Amazon's Raw 53. We can integrate with things like [Venify 00:16:47] to automatically configure and pick up SSL certificate through an application. The point is that by integrating with these surrounding ecosystems, that enables us that the application owner uploads the application and it just works. How it worked, they don't really need to know, they don't really need to care, but the firewalls could instantiate, the IP addressing could be automatically inherited. DDNS could automatically be registered. All of these elements. Many of these elements are something that Avi has natively baked in, but you can also provide some customization because Avi built on top of a rest API. That means that what you see in the FUI and what you see from the CLI are actually just wrappers for the API. If you're using the GUI, you can right click, click on inspect elements and start mousing over or clicking through the UI and you'll see the API calls that your browser was actually sending and the JSON response that Avi is sending back. Your browser will take that JSON formatted result, put it into a style sheet, shake it up and there is the web page that you see rendered from the GUI. The same is true from the CLI. You can add a -API flag and you'll actually see the API calls that are being exchanged underneath. The point of this is that it makes it really easy for customers to automate everything on hobby. There's nothing that the API doesn't have access to. Everything we do is exclusively done through the API. That makes it really easy for you to go and build out some customization if that's going to be through Terraform, through Ansible, through VRO VRA, or just custom Python scripts. This is something that most every Avi customer is looking at, some form of automation, some sort of way to be able to do more with less. As they deploy more and more applications, this is the core underlying element that really has them looking around and trying to figure out how can I do something better? How can I do something more efficiently? That's why they're looking at other load balancers in the first place. So this is a really key component as to why Avi, so that's something that's really important, is that even if the person that you're talking to is not an API person, what's important about Avi that yes, we have APIs. We have APIs for everything. However, it's really what you don't have to do, what you don't have to code. The fact that Avi automatically can handle things like the capacity management of service engines, the integration with the surrounding ecosystems or cloud environments to talk to AWS to go and spin up more capacity or to handle multiple availability zones, these are things that are traditional load balancers, each and every one of these steps, each and every one of these integrations are something that you, the administrator, would have to do manually. Each and every one of these is something that you have a probability of failure. You have a steep learning curve and it's something where customers are feeling like even though they're buying an off the shelf hardware appliance load balancer, it's still a do it yourself project if you want to do any kind of intelligence on top of this. This is the point with Avi, is that out of the box it automatically does everything that they need it to do, everything that they were looking at doing. It's these massive projects for the next year. As soon as they see Avi, they realize it's already been done and you just have to double click and start the install and away you go.
- Driving forces: Digital enterprises need to deliver more applications, faster, and at lower cost Consistent multi-cloud deployments across data centers and public clouds with enterprise level security Shift towards cloud-native apps and automation to support DevOps and CI/CD processes