A financial technology company is planning the network architecture for a global payment processing service. External payment gateways will communicate with backend Compute Engine instances deployed across multiple Google Cloud regions using a proprietary, non-HTTP raw TCP protocol. The company wants to terminate incoming TCP connections at the Google network edge close to clients to reduce latency and distribute incoming traffic across the multi-region backend instances. Which Google Cloud load balancer should the company select?
- External Proxy Network Load BalancerCevap
- BExternal HTTP(S) Load Balancer
- CInternal Passthrough Network Load Balancer
- DCloud DNS Private Zone
Cevap
The External Proxy Network Load Balancer is the correct choice because it supports global external non-HTTP TCP traffic and terminates client TCP connections at the Google edge network.
The External Proxy Network Load Balancer is designed for external, non-HTTP raw TCP or SSL traffic. It operates globally, terminating TCP connections at Google's network edge to optimize latency before forwarding connections to Compute Engine backends in multiple regions.
Adım Adım Çözüm
Anahtar Kavram
Selecting GCP Load Balancers based on Traffic Scope and Protocol