Network load balancers
Distribute user traffic among VM instances and servers
Ensure systems do not get overwhelmed and all requests are easily and efficiently handled with network load balancers from Google Cloud.
New customers get $300 in free credits on signup to apply towards deploying a preconfigured VM cluster solution.
Overview
What does a load balancer do?
A network load balancer distributes user traffic among virtual machine (VM) instances in the same region. A network load balancer can receive traffic from any client on the internet, Google Cloud VMs with external IPs, and VMs that have internet access through Cloud NAT or instance-based NAT.
What types of load balancers are there?
There are two primary types of load balancers: external and internal load balancers. On Google Cloud, external load balancers distribute traffic coming from the internet to your Virtual Private Cloud (VPC) network. Internal load balancers distribute traffic to instances inside of Google Cloud.
Application load balancing vs network load balancing
Application load balancing or the application load balancer (ALB) operate at layer 7, the application layer. ALBs inspects application level content and routes based on HTTPs and HTTP. Network load balancing or the network load balancer operates at layer 4. NLB routes IP protocols TCP and UDP.
What are the benefits of network load balancing?
Network load balancing allows you to scale as users and traffic grow, easily and automatically balancing huge, unexpected, and instantaneous traffic spikes. Autoscaling helps your applications instantly handle increases in traffic and reduces cost when fewer resources are needed.
What is Google Cloud’s load balancing service?
Google Cloud offers Cloud Load Balancer, a fully distributed, software-defined, managed service that doesn’t require hardware. Cloud Load Balancing is built on the same infrastructure that powers Google, supporting 1 million+ queries per second with consistent high performance and low latency. And Cloud CDN for HTTP(S) load balancing enables optimizing application delivery for your users with a single checkbox.
What type of traffic does network load balancing handle?
Network load balancing handles internal and external traffic. Specifically, you can configure a network load balancer for TCP, UDP, ESP, GRE, ICMP, and ICMPv6 traffic.
How It Works
Load balancing uses a load balancer to receive user traffic and automatically distributes it among multiple servers or VM instances in the same region. Google Cloud’s load balancer diverts heavy or unexpected spikes in user traffic to reduce the risk of overloading a host and increase application availability.
Load balancing uses a load balancer to receive user traffic and automatically distributes it among multiple servers or VM instances in the same region. Google Cloud’s load balancer diverts heavy or unexpected spikes in user traffic to reduce the risk of overloading a host and increase application availability.
Common Uses
Load balancing VMs
Configure load balancing VMs
Learn how to configure Internal HTTP(S) Load Balancing for your services that run on Compute Engine VMs. Setting up an internal HTTP(S) load balancing with VM instance group backends includes performing prerequisite tasks and setting up the load balancer resources.
How-tos
Configure load balancing VMs
Learn how to configure Internal HTTP(S) Load Balancing for your services that run on Compute Engine VMs. Setting up an internal HTTP(S) load balancing with VM instance group backends includes performing prerequisite tasks and setting up the load balancer resources.
Network and HTTP load balancers
Set up network and HTTP load balancers
Learn how to tell the differences between a network load balancer and an HTTP load balancer and how to set them up for your applications running on Compute Engine VMs. This lab teaches you to set up network load balancers and HTTP(s) Load Balancer.
How-tos
Set up network and HTTP load balancers
Learn how to tell the differences between a network load balancer and an HTTP load balancer and how to set them up for your applications running on Compute Engine VMs. This lab teaches you to set up network load balancers and HTTP(s) Load Balancer.
Three-tier web services
Support traditional three-tier web services
Internal HTTP(S) load balancing can support traditional three-tier web services. The diagram shows how you can use three types of Google Cloud load balancers to scale three tiers.
How-tos
Support traditional three-tier web services
Internal HTTP(S) load balancing can support traditional three-tier web services. The diagram shows how you can use three types of Google Cloud load balancers to scale three tiers.
External TCP/UDP network load balancing
Set up a network load balancer with a backend service
Create a basic Network Load Balancing deployment using a regional backend service that supports either TCP or UDP traffic. For TCP, UDP, ESP, GRE, ICMP, and ICMPv6 traffic (not just TCP or UDP), use the guide to set up a network load balancer for multiple IP protocols.
How-tos
Set up a network load balancer with a backend service
Create a basic Network Load Balancing deployment using a regional backend service that supports either TCP or UDP traffic. For TCP, UDP, ESP, GRE, ICMP, and ICMPv6 traffic (not just TCP or UDP), use the guide to set up a network load balancer for multiple IP protocols.
Internal HTTP(S) load balancing
Internal HTTP(S) load balancing overview
Internal HTTP(S) load balancing is a proxy-based, regional Layer 7 load balancer that enables you to run and scale your services behind an internal IP address, distributing HTTP and HTTPS traffic to backends hosted on Compute Engine, Google Kubernetes Engine (GKE), and Cloud Run. The load balancer is accessible only in the chosen region of your Virtual Private Cloud (VPC) network on an internal IP address.
How-tos
Internal HTTP(S) load balancing overview
Internal HTTP(S) load balancing is a proxy-based, regional Layer 7 load balancer that enables you to run and scale your services behind an internal IP address, distributing HTTP and HTTPS traffic to backends hosted on Compute Engine, Google Kubernetes Engine (GKE), and Cloud Run. The load balancer is accessible only in the chosen region of your Virtual Private Cloud (VPC) network on an internal IP address.
Start your proof of concept
New customers get $300 in free credits
Get fully managed, scalable load balancing
Set up external HTTP(S) load balancer
Set up an internal TCP/UDP load balancer
