Network Load Balancer

Related topics

• Application Load Balancers is an alternative to Network Load Balancer From the official documentation: “You'd choose an Application Load Balancer when you need a Layer 7 load balancer for your applications with HTTP(S) traffic. You'd choose a Network Load Balancer when you need a Layer 4 load balancer that supports TLS offloading (with a proxy load balancer) or you need support…”
• forwarding rule is part of Network Load Balancer From the official documentation: “- A network load balancer with a forwarding rule.”
• Network Load Balancer is part of Cloud Load Balancing From the official documentation: “Cloud Load Balancing offers two types of load balancers: Application Load Balancers and Network Load Balancers.”
• backend service is part of internal passthrough Network Load Balancer From the official documentation: “An internal passthrough Network Load Balancer's backend service is regional.”
• Application Load Balancer works with Service Extensions From the official documentation: “This page describes how to configure Service Extensions with Application Load Balancers for advanced use cases.”
• forwarding rule depends on backend service From the official documentation: “Create a forwarding rule for the backend service.”
• forwarding rule is part of internal passthrough Network Load Balancer From the official documentation: “An internal passthrough Network Load Balancer has a frontend (the forwarding rule) and a backend (the backend service).”
• backend service is part of Cloud Service Mesh From the official documentation: “you create a new backend service in Cloud Service Mesh.”
• backend service works with forwarding rule From the official documentation: “Connect the forwarding rule to the backend service.”
• Cloud Load Balancing works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh works with Cloud Load Balancing to provide a managed ingress experience.”
• backend service configures Cloud Service Mesh From the official documentation: “Backend services are configuration resources that provide information to Cloud Service Mesh, including the backends, such as managed instance groups, to which the backend service routes traffic.”
• Cloud Load Balancing works with Service Extensions From the official documentation: “GKE uses Service Extensions to add custom logic into Cloud Load Balancing.”
• forwarding rule is part of Application Load Balancer From the official documentation: “Create the IPv6 forwarding rule for the application load balancer.”
• forwarding rule works with internal passthrough Network Load Balancer From the official documentation: “You have a forwarding rule to direct network traffic to an internal passthrough Network Load Balancer whose backends provide packet mirroring.”
• internal passthrough Network Load Balancer depends on backend service From the official documentation: “A backend service is necessary for creating an internal passthrough Network Load Balancer.”
• Application Load Balancer works with backend service From the official documentation: “While integrating a backend service with Application Load Balancer, it's important to measure the performance of a backend service on its own, in the absence of a load balancer.”
• Application Load Balancer is part of Cloud Load Balancing From the official documentation: “To see an overview of all the Cloud Load Balancing products available, see [Cloud Load Balancing overview](/load-balancing/docs/load-balancing-overview). To determine which Cloud Load Balancing product to use, you must first determine the traffic type that your load balancers…”
• Application Load Balancers is part of Cloud Load Balancing From the official documentation: “Cloud Load Balancing offers two types of load balancers: Application Load Balancers and Network Load Balancers.”
• Application Load Balancers works with Service Extensions From the official documentation: “You can use Service Extensions with Application Load Balancers and Media CDN as follows:”
• backend service is part of Cloud Load Balancing From the official documentation: “Quotas and limits for Cloud Load Balancing resources such as forwarding rules, backend services, and more.”
• backend service configures Cloud Load Balancing From the official documentation: “A [backend service](/compute/docs/reference/rest/v1/backendServices) defines how Cloud Load Balancing distributes traffic.”
• backend service is an alternative to forwarding rule From the official documentation: “You can enable IAP on a Compute Engine [backend service](/load-balancing/docs/backend-service) or on a Compute Engine [forwarding rule](/load-balancing/docs/forwarding-rule-concepts).”
• Cloud Load Balancing is an alternative to Cloud Service Mesh From the official documentation: “If you want to use [Cloud Load Balancing, Ingress, or Cloud Service Mesh to handle the SSL configuration](/migrate/containers/docs/windows/prepare-windows-cluster#secure-access), then you need to set `protocol` to `http`:”
• Cloud Service Mesh depends on forwarding rule From the official documentation: “Cloud Service Mesh then looks for forwarding rules that have the `INTERNAL_SELF_MANAGED` load-balancing scheme and reference the same VPC network name.”
• Cloud Service Mesh works with forwarding rule From the official documentation: “Cloud Service Mesh then looks for forwarding rules that have the `INTERNAL_SELF_MANAGED` load-balancing scheme and reference the same VPC network name.”
• forwarding rule is part of Cloud Load Balancing From the official documentation: “Google Cloud load balancing uses forwarding rule resources to match certain types of traffic and forward it to a load balancer.”
• internal passthrough Network Load Balancer is part of Cloud Load Balancing From the official documentation: “The NAT gateways are configured as backends of an internal load balancer with a new default route, which has an [internal passthrough Network Load Balancer from Cloud Load Balancing as the next hop](/load-balancing/docs/internal/ilb-next-hop-overview).”