Google Cloud Platform : Network and Load Balancer

Google Cloud external TCP/UDP Network Load equalisation (after this stated as Network Load Balancing) may be a regional, pass-through load balancer. A network load balancer distributes external traffic among virtual machine (VM) instances within the same region.

You can put together a network load balancer for TCP, UDP, ESP, and ICMP traffic. Support for psychic phenomena and ICMP is in Preview.

A network load balancer will receive traffic from:
1.Any shopper on the net
2.Google Cloud VMs with external IPs
3.Google Cloud VMs that have web access through Cloud NAT or instance-based NAT

Network Load equalisation has the subsequent characteristics:
1. Network Load equalisation may be a managed service.
2. Network Load equalisation is enforced by victimization Andromeda virtual networking and Google rail technology.
3. Network load balancers don't seem to be proxies.
a. Load-balanced packets ar received by backend VMs with the packet's supply and destination scientific discipline addresses, b. protocol, and, if the protocol is port-based, the supply and destination ports unchanged.
b. Load-balanced connections ar terminated by the backend VMs.
c. Responses from the backend VMs go on to the purchasers, not back through the load balancer. The trade term for this is often direct server come.

Scope
A network load balancer balances traffic originating from the net.
The scope of a network load balancer is regional, not global. this implies that a network load balancer cannot span multiple regions. inside one region, the load balancer services all zones.