Load balancing and scaling
Trusted Cloud by S3NS offers load balancing and autoscaling for
groups of instances.
Load balancing
Trusted Cloud offers server-side load balancing so you can distribute
incoming traffic across multiple virtual machine (VM) instances. Load
balancing provides the following benefits:
- Scale your app
- Support heavy traffic
- Detect and automatically remove unhealthy VM instances using
health checks. Instances that
become healthy again are automatically re-added.
- Route traffic to the closest virtual machine
Trusted Cloud load balancing uses forwarding rule
resources to match certain types of traffic and forward it to a load balancer.
For example, a forwarding rule can match TCP traffic destined to port 80 on IP
address 192.0.2.1, then forward it to a load balancer, which then directs
it to healthy VM instances.
Trusted Cloud load balancing is a managed service, which means its
components are redundant and highly available. If a load balancing component
fails, it is restarted or replaced automatically and immediately.
Trusted Cloud offers several different types of load balancing that
differ in
capabilities, usage scenarios, and how you configure them. See
Trusted Cloud load balancing documentation
for descriptions.
Autoscaling
Compute Engine offers autoscaling to automatically add or remove VM
instances from a
managed instance group (MIG)
based on increases or decreases in load. Autoscaling lets your apps gracefully
handle increases in traffic, and it reduces cost when the need for resources is
lower. You can autoscale a MIG based on its CPU utilization, Cloud Monitoring
metrics, schedules, or load balancing serving capacity.
When you set up an autoscaler to scale based on load balancing serving capacity,
the autoscaler watches the serving capacity of an instance group and scales
when the VM instances are over or under capacity. The serving capacity of an
instance can be defined in the load balancer's
backend service and can be
based on either utilization or requests per second. For more information, see
Scaling based on load balancing serving capacity.
To learn more about autoscaling, see Autoscaling groups of instances.
What's next
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-26 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eGoogle Cloud offers server-side load balancing to distribute incoming traffic across multiple virtual machine instances, ensuring high availability and scalability.\u003c/p\u003e\n"],["\u003cp\u003eThe load balancing service uses forwarding rules to direct specific types of traffic to a load balancer, which then routes it to healthy VM instances.\u003c/p\u003e\n"],["\u003cp\u003eAutoscaling in Compute Engine automatically adjusts the number of VM instances in a managed instance group based on various factors such as CPU utilization, Cloud Monitoring metrics, schedules, or load balancing serving capacity.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Cloud's autoscaling feature can scale based on the serving capacity of the instance group, defined in the load balancer's backend service, which can use either utilization or requests per second as metrics.\u003c/p\u003e\n"]]],[],null,["# Load balancing and scaling\n\n*** ** * ** ***\n\nGoogle Cloud offers load balancing and autoscaling for\n[groups of instances](/compute/docs/instance-groups).\n\nLoad balancing\n--------------\n\nGoogle Cloud offers server-side load balancing so you can distribute\nincoming traffic across multiple virtual machine (VM) instances. Load\nbalancing provides the following benefits:\n\n- Scale your app\n- Support heavy traffic\n- Detect and automatically remove unhealthy VM instances using [health checks](/load-balancing/docs/health-check-concepts). Instances that become healthy again are automatically re-added.\n- Route traffic to the closest virtual machine\n\nGoogle Cloud load balancing uses forwarding rule\nresources to match certain types of traffic and forward it to a load balancer.\nFor example, a forwarding rule can match TCP traffic destined to port 80 on IP\naddress `192.0.2.1`, then forward it to a load balancer, which then directs\nit to healthy VM instances.\n\nGoogle Cloud load balancing is a managed service, which means its\ncomponents are redundant and highly available. If a load balancing component\nfails, it is restarted or replaced automatically and immediately.\n\nGoogle Cloud offers several different types of load balancing that\ndiffer in\ncapabilities, usage scenarios, and how you configure them. See\n[Google Cloud load balancing documentation](/load-balancing/docs)\nfor descriptions.\n\nAutoscaling\n-----------\n\nCompute Engine offers autoscaling to automatically add or remove VM\ninstances from a\n[managed instance group (MIG)](/compute/docs/instance-groups#managed_instance_groups)\nbased on increases or decreases in load. Autoscaling lets your apps gracefully\nhandle increases in traffic, and it reduces cost when the need for resources is\nlower. You can autoscale a MIG based on its CPU utilization, Cloud Monitoring\nmetrics, schedules, or load balancing serving capacity.\n\nWhen you set up an autoscaler to scale based on load balancing serving capacity,\nthe autoscaler watches the serving capacity of an instance group and scales\nwhen the VM instances are over or under capacity. The serving capacity of an\ninstance can be defined in the load balancer's\n[backend service](/load-balancing/docs/backend-service) and can be\nbased on either utilization or requests per second. For more information, see\n[Scaling based on load balancing serving capacity](/compute/docs/autoscaler/scaling-load-balancing).\n\nTo learn more about autoscaling, see [Autoscaling groups of instances](/compute/docs/autoscaler).\n\nWhat's next\n-----------\n\n- Learn more about [instance groups](/compute/docs/instance-groups).\n- Learn how to [autoscale managed instance groups](/compute/docs/autoscaler) based on:\n - [CPU utilization](/compute/docs/autoscaler/scaling-cpu)\n - [Load balancing serving capacity](/compute/docs/autoscaler/scaling-load-balancing)\n - [Monitoring metrics](/compute/docs/autoscaler/scaling-stackdriver-monitoring-metrics)\n - [Schedules](/compute/docs/autoscaler/scaling-schedules)\n- Learn how to [choose a load balancer](/load-balancing/docs/choosing-load-balancer) and\n - How to [set up an external Application Load Balancer](/load-balancing/docs/https/setting-up-https)\n - How to [set up an external passthrough Network Load Balancer](/load-balancing/docs/network/setting-up-network)"]]
