GCP中的网络和HTTP(s)负载均衡器之间有什么区别

Question

GCP提供两个负载平衡器,即网络和HTTP,其中前者在第4 层工作,后者在第7层工作.

还有一个文档说明即使HTTP流量也可以由网络负载平衡器进行负载平衡.这略微混淆了为GCP中的Web应用程序选择哪个负载均衡器.在为项目选择一个之前,最好先了解这些差异.

基于工作流程,设置,基于区域/区域,会话亲和性选项以及其他设置,它们之间有何区别？

Answer 1

网络负载均衡器VS HTTP(s)负载均衡器

+---------------------+------------------------------------------+------------------------------------------------------+
|       Category      |       Network Load Balancing (NLB)       |             HTTP(S) Load Balancing (HLB)             |
+---------------------+------------------------------------------+------------------------------------------------------+
|     1. Region /     | NLB supports only within a region.       | HLB supports both within cross-region                |
|     Cross-Region    | Does not support cross-region            | load balancing.                                      |
|                     | load balancing                           |                                                      |
+---------------------+------------------------------------------+------------------------------------------------------+
|  2. Load balancing  | NLB is based on IP address, port         | HLB is based only on HTTP and HTTPS                  |
|       based on      | and protocol type. Any TCP/UDP           | protocols.                                           |
|                     | traffic, even SMTP can be                |                                                      |
|                     | load balanced.                           |                                                      |
+---------------------+------------------------------------------+------------------------------------------------------+
|      3. Packet      | Packet inspection is possible and        | HLB cannot inspect packets.                          |
|      inspection     | load balance based on packets            |                                                      |
+---------------------+------------------------------------------+------------------------------------------------------+
|     4. Instance     | No need of creating instance group.      | Managed / UnManaged Instance group                   |
|         Group       | Target pools need to be created.         | is necessary for creating HTTP / HTTPS               |
|                     | Instance can be just tagged to the pool. | load balancer.                                       |
|                     | Ideal for unmanaged instance group       |                                                      |
|                     | where instances are non homogeneous.     |                                                      |
+---------------------+------------------------------------------+------------------------------------------------------+
|     5. Workflow     | Forwarding rules is the starting point.  | This is quite complex in HTTP(s) load balancer.      |
|                     | It directs the request to the            | Global forwarding rulesroutes direct the request     |
|                     | target pools from which compute          | to target HTTP proxy, which in turn checks the       |
|                     | engines will pick the request.           | URL map to determine appropriate backend             |
|                     |                                          | services.  These services in turn direct the request |
|                     | Forwarding rules -> target pool          | to the instance group.                               |
|                     |  -> instances                            |                                                      |
|                     |                                          |                                                      |
|                     |                                          | Global forwarding rules -> Target HTTP proxy ->      |
|                     |                                          | URL map -> Backend Sevices -> instance group         |
+---------------------+------------------------------------------+------------------------------------------------------+
|     6. Types of     | Basic network load balancer which        | 1. Cross-region load balancer uses only one          |
|    load balancer    | directs the request based on IP address, | global IP address and routes the request             |
|                     | port and the protocol within the region. | to the nearest region.                               |
|                     |                                          |                                                      |
|                     |                                          | 2. Content-based load balancer is based              |
|                     |                                          | on the URL path. Different path rules need           |
|                     |                                          | different backend services. for eg: /video           |
|                     |                                          | and /static require two separate backend services.   |
+---------------------+------------------------------------------+------------------------------------------------------+
| 7. Session affinity | Session affinity can be set, but only    | 1. Client IP Affinity: This directs the same         |
|                     | during the creation of target pool.      | client ip to same backend instance by                |
|                     | Once it is set, the value                | computing hash of the IP.                            |
|                     | cannot be changed.                       | 2. Generated Cookie Affinity: Load balancer stores   |
|                     |                                          | cookie in clients and directs the same client to     |
|                     |                                          | same instance with the help of retrieved cookie.     |
+---------------------+------------------------------------------+------------------------------------------------------+
|   8. Health check   | Health check is optional, but network    | Health can be verified by either using HTTP          |
|                     | load balancing relies on HTTP Health     | heath check or HTTPS health check.                   |
|                     | checks for determining instance health.  |                                                      |
+---------------------+------------------------------------------+------------------------------------------------------+

上表基于我的观点.如果有任何不正确或如果我错过了什么,请随时发表评论,我会将其添加到表格中.

以下是有关在GCP中设置HTTP负载均衡器的说明的链接.

Answer 2

一般来说，以下是网络负载均衡器和 Http 负载均衡器之间的区别。

\n\n

网络负载均衡器（第 4 层）： \n这是基于网络变量（例如 IP 地址和目标端口）的流量分配。它位于第 4 层 (TCP) 及以下层，设计时并未考虑应用程序层的任何内容，例如内容类型、cookie 数据、自定义标头、用户位置或应用程序行为。它与上下文无关，只关心它以这种方式引导的数据包中包含的网络层信息。

\n\n

应用程序负载均衡器（第 7 层） \n 这是基于多个变量的请求分配，从网络层到应用程序层。它具有上下文感知能力，可以像基于变量组合一样轻松地基于任何单个变量来定向请求。应用程序根据其特殊行为进行负载平衡，而不仅仅是服务器（操作系统或虚拟化层）信息。提供基于规则、基于主机或基于路径路由 HTTP 和 HTTPS 流量的能力。与 NLB 一样，每个目标可以位于不同的端口上。

\n\n

两者之间的另一个区别很重要，因为网络负载平衡无法确保应用程序的可用性。这是因为它的决策仅基于网络和 TCP 层变量，并且根本不了解应用程序。通常，网络负载均衡器将根据服务器响应 ICMP ping 或正确完成三向 TCP 握手的能力来确定 \xe2\x80\x9cavailability\xe2\x80\x9d。应用程序负载均衡器更深入，不仅能够根据特定页面的成功 HTTP GET 来确定可用性，还能够根据输入参数验证内容是否符合预期来确定可用性。

\n\n

参考： https: //medium.com/awesome-cloud/aws-difference- Between -application-load-balancer-and-network-load-balancer-cb8b6cd296a4

\n