Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Google Cloud menawarkan load balancing dan penskalaan otomatis untuk
grup instance.
Load balancing
Google Cloud menawarkan load balancing sisi server sehingga Anda dapat mendistribusikan
traffic masuk di beberapa instance virtual machine (VM). Load
balancing memberikan manfaat berikut:
Menskalakan aplikasi
Mendukung traffic padat
Mendeteksi dan menghapus instance VM yang tidak responsif secara otomatis menggunakan health check. Instance yang
menjadi responsif kembali akan otomatis ditambahkan kembali.
Mengarahkan traffic ke virtual machine terdekat
Load balancingGoogle Cloud menggunakan resource aturan penerusan
untuk mencocokkan jenis traffic tertentu dan meneruskannya ke load balancer.
Misalnya, aturan penerusan dapat mencocokkan traffic TCP yang ditujukan ke port 80 di alamat IP 192.0.2.1, lalu meneruskannya ke load balancer, yang kemudian mengarahkannya ke instance VM yang responsif.
Load balancingGoogle Cloud adalah layanan terkelola, yang berarti
komponennya redundan dan sangat tersedia. Jika gagal, komponen load balancing
akan dimulai ulang atau akan otomatis dan segera diganti.
Google Cloud menawarkan beberapa jenis load balancing dengan berbagai
kemampuan, skenario penggunaan, dan cara Anda mengonfigurasinya. Lihat
dokumentasi load balancingGoogle Cloud
untuk mengetahui deskripsinya.
Penskalaan otomatis
Compute Engine menawarkan penskalaan otomatis untuk secara otomatis menambahkan atau menghapus
instance VM dari
grup instance terkelola (MIG)
berdasarkan peningkatan atau penurunan muatan. Dengan penskalaan otomatis, aplikasi Anda dapat
menangani peningkatan traffic dengan baik, dan mengurangi biaya saat kebutuhan resource
lebih rendah. Anda dapat menskalakan MIG secara otomatis berdasarkan pemakaian CPU, metrik
Cloud Monitoring, jadwal, atau kapasitas penyaluran load balancing.
Saat Anda menyiapkan autoscaler untuk menskalakan berdasarkan kapasitas penyaluran load balancing,
autoscaler akan memantau kapasitas penyaluran grup instance dan menskalakan
saat kapasitas instance VM melebihi atau kurang. Kapasitas penyaluran
instance dapat ditentukan di
layanan backend load balancer dan dapat
didasarkan pada pemakaian atau permintaan per detik. Untuk informasi selengkapnya, lihat
Menskalakan berdasarkan kapasitas penyaluran load balancing.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 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)"]]
