Kepriye cara kerja load balancing ing AWS?

Question

Accepted Answer

**Elastic Load Balancing (ELB)** nglumpukake traffic sing teka ing ngisor target cacahe (EC2 instances, containers, lsp.) — nambahi **availability** (ora ana single point of failure) lan **scalability** (traffic wis kasebar). Iki dadi komponen penting kanggo aplikasi sing reliable lan scalable.

## Apa sing didadekake load balancer

```text
A LOAD BALANCER sits in front of multiple backend targets and distributes requests:
  Client → LOAD BALANCER → ┬→ Instance 1
                           ├→ Instance 2
                           └→ Instance 3
  → spreads traffic across targets (scalability + no single instance overloaded)
  → HEALTH CHECKS: routes only to HEALTHY targets (an unhealthy one is bypassed)
  → if a target fails, traffic goes to the others → HIGH AVAILABILITY
  → single entry point (clients hit the LB, not individual instances)
```

## Jenis-jenis AWS load balancers

```text
APPLICATION LB (ALB) → Layer 7 (HTTP/HTTPS): content/path/host-based routing,
  great for web apps, microservices, containers (route /api → one group, /app → another)
NETWORK LB (NLB) → Layer 4 (TCP/UDP): ultra-high performance, low latency, static IPs
GATEWAY LB → for deploying virtual network appliances
(Classic LB → legacy)
→ ALB is the common choice for HTTP applications.
```

## Fitur-fitur penting

```text
✓ HEALTH CHECKS — detect unhealthy targets and stop routing to them (reliability)
✓ Spread across MULTIPLE AZs — survive an AZ failure
✓ Works with AUTO SCALING — automatically includes new instances as they scale
✓ SSL/TLS termination (handle HTTPS at the LB)
✓ Sticky sessions, path/host routing (ALB), WebSocket support
```

## Kepentingane

Paham load balancing iku berharga amarga dadi komponen penting kanggo mbangun aplikasi sing **reliable lan scalable** ing AWS, dadi iki pengetahuan praktis sing penting.

Load balancer ngatasi rong kabutuhan fundamental: **availability** (kanthi nglumpukake traffic nglawati target backend cacahe kanthi **health checks** sing direct traffic mung menyang target sing sehat, dadi yen siji instance mangga, traffic terus menyang liyane — ngilangi single points of failure) lan **scalability** (kasebar load nglawati instances cacahe supaya ora siji sing kebeban, lan nyedhiyake siji entry point).

Iki bikin load balancing penting kanggo aplikasi apa wae sing butuh handle traffic signifikan kanthi reliable.

Paham **jenis-jenise** — **Application Load Balancer (ALB)** kanggo Layer 7 HTTP/HTTPS kanthi content/path/host-based routing (pilihan umum kanggo aplikasi web lan microservices), **Network Load Balancer (NLB)** kanggo Layer 4 ultra-high-performance TCP/UDP — tulung pilih sing tepat.

Paham **fitur-fitur penting** iki penting: health checks (kanggo reliability), kasebar nglawati **multiple AZs** (selamat saka AZ failures, bisa dipadakke kanthi high-availability pattern), integrasi kanthi **auto scaling** (otomatis kalebu instances anyar nalika scale — dadi load balancing lan auto scaling bekerja bareng kanggo aplikasi sing elastic lan resilient), lan SSL/TLS termination.

Gabungan load balancing + auto scaling + multi-AZ deployment iku pola foundational kanggo aplikasi AWS sing scalable lan highly-available.

Amarga aplikasi reliable lan scalable butuh nglumpukake traffic nglawati instances cacahe (kanggo availability lan scale), lan amarga ELB (kanthi jenis-jenise, health checks, multi-AZ spread, lan auto-scaling integration) iku mekanisme kanggo iki, paham load balancing iku berharga, pengetahuan AWS yang penting secara praktis — komponen core ing arsitektur cloud sing resilient sing bekerja sareng-sareng kanthi auto scaling lan multi-AZ deployment kanggo mbangun aplikasi sing handle traffic real-world kanthi reliable lan skala gede.