为内部和外部用户GCP服务的负载均衡服务 [英] Load balanced service serving both internal and external users GCP

问题描述

我们正在GCP上设置服务，该服务将满足Internet和VPC内部其他服务的请求.

We are in the process of setting up a service on GCP that will serve requests from both the internet and from other services inside of our VPC.

我们已经有一个全局负载平衡器设置，并且希望对我们新服务的所有流量也进行负载平衡.

We already have a global load-balancer setup and want all traffic to our new service to be load-balanced as well.

在尝试使用新服务时，是否建议我们的内部服务使用全局LB地址?还是我们应该在全局LB后面设置内部LB以便内部服务使用?

Is it advisable to have our internal services use the global LB address when trying to reach the new service? Or should we be setting up internal LBs behind the global LB for internal services to use?

如果我们要同时使用全局LB用于内部和外部客户端，那么与使用内部LB相比，在性能方面是否有不利之处?

If we were to use the global LB for both internal and external clients, are there any performance disadvantages compared to using and internal LB?

感谢，感谢您的帮助！

推荐答案

并行使用两个负载平衡器(因为它们彼此独立). Internet的全局负载均衡器和VPC访问的内部负载均衡器.类型(HTTP/TCP)取决于您要提供的流量.考虑第7层(HTTP)与第3/4层(TCP/UDP).

Use two load balancers in parallel (as in they are independent of each other). The Global Load Balancer for the Internet and the Internal Load Balancer for VPC access. The type (HTTP/TCP) depends on the traffic you want to serve. Think Layer 7 (HTTP) versus Layer 3/4 (TCP/UDP).

对于VPC访问，使用内部负载平衡器具有性能优势.最大的是跳数的减少(VPC-> Internet->负载均衡器-> VPC).第二个是您的VPC网络速度更快，停留在VPC内.

For VPC access there are performance advantages using an Internal load balancer. The biggest is a reduction in the number of hops (VPC -> Internet -> Load Balancer -> VPC). The second is that your VPC network speed is faster staying within the VPC.

这篇关于为内部和外部用户GCP服务的负载均衡服务的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！