Google Network Load Balancing
About Google Network Load Balancing
Network load balancing can spread TCP and UDP based traffic over a pool of instances within a Compute Engine region. Its health check helps ensure only healthy instances are used to handle the traffic. It is scalable and does not require pre-warming.
Network load balancing uses forwarding rules that point to target pools, which list the instances available for load balancing and define which type of health check that should be performed on these instances. See the network load balancing scenario for more information.
Network load balancing offers some load balancing options that are not available with HTTP(S) load balancing. For example, you can load balance additional TCP/UDP-based protocols such as SMTP traffic. If your application is interested in TCP-connection-related characteristics, network load balancing allows your app to inspect the packets, which you cannot do with HTTP(S) load balancing.
You can also use network load balancing to handle HTTPS traffic. You will need to:
If you need cross-regional load balancing, use HTTP(S) load balancing.