Cloud Load Balancing

Key Takeaways

How do your customers get to your application when it might be provided by four VMs at one moment and 40 VMs at another? That's done through cloud load [Music] balancing. The job of a load balancer is an important one. It distributes user traffic across multiple instances of an application. Distributing the load reduces the risk of applications experiencing performance issues. Cloud load balancing is a fully distributed softwaredefined managed service for all your traffic. Because the load balancers don't run in VMs, you don't have to worry about scaling or managing them. You can put cloud load balancing in front of all your traffic. HTTP or HTTPS, other TCP and SSL traffic and UDP traffic too. Car traffic not advised. Cloud load balancing provides cross-reional load balancing, including automatic multi-reion failover, which gently moves traffic in fractions if backends become unhealthy. Reaction time is quick, too. Whether it be a change in users, traffic, network, backend health, or other related conditions. And what if you anticipate a huge spike in demand? Say your online game is already a hit. Do you need to file a support ticket to warn Google of the incoming load? No. No so-called pre-warming is required. VPC offers a suite of load balancing options. If you need cross regional load balancing for a web application, use global HTTPS load balancing. For secure sockets layer traffic that is not HTTP, global SSL proxy is the move. TCP traffic that doesn't use SSL, global TCP proxy. Those last two proxy services only work for specific port numbers and they only work for TCP. If you want to load balance UDP traffic or traffic on any port number, you can still load balance across a Google Cloud region with the regional external pass through network load balancer. That was a mouthful. On top of that, you can also deploy regional external application load balancer and proxy network load balancer. Give me a chance to catch my breath. Now, all those services have something in common. They're intended for traffic coming into the Google Cloud network from the internet. But what if you want to balance traffic inside your project, say between the presentation layer and the business layer of your application? Well, you can do that too. Use the regional internal load balancer that supports proxy network load balancer. passed through network load balancer and application load balancer. It accepts traffic on a Google Cloud internal IP address and load balances it across Google Cloud VMs. All right, one more load balancer for now. The Google Cloud Cross region internal load balancer is a layer 7 load balancer and you can use it to load balance traffic to back-end services that are globally distributed including traffic management that ensures traffic is directed to the closest backend. Okay, so that's a lot of load balancers. Whatever your needs might be, Google Cloud is here to help distribute user traffic. Next up is Cloud DNS and Cloud CDN.