Pija cara kanggo scale layanan individu lan nemokake bottleneck kinerja?

Question

Accepted Answer

Kauntungan utama microservices yaiku **scale saben layanan kanthi independen** kanggo cocog karo beban dhewe, tinimbang scale kabeh aplikasi. Nemokake bottleneck iku mesine perkara pengukuran per-layanan lan per-hop.

## Teknik scaling

- **Horizontal scaling** — nambahi instans stateless ing mburi load balancer.
- **Autoscaling** — scale ing CPU, memori, kedalaman antrian, utawa metrik custom.
- **Caching** — kurangi pekerjaan terulang lan beban downstream.
- **Async + queues** — serap lonjakan; pisahkan pekerjaan alon.
- **Data scaling** — read replicas, sharding, panyekel per-layanan.

```yaml
# Kubernetes HPA: scale orders on CPU
minReplicas: 3
maxReplicas: 20
metric: cpu
targetUtilization: 70   # add pods when avg CPU > 70%
```

## Nemokake bottleneck

```text
1. Metrics: which service has high latency / saturation? (RED/USE)
2. Traces: which SPAN in the request is slow?
3. Drill in: DB query? lock? N+1 calls? GC pause?
```

```text
Gateway ──┤ Orders ──┤ Payments ████████████ ← 80% of latency here
                       Inventory ─┤
```

## Bottleneck umum

```text
⚠️ Chatty synchronous calls (fan-out per request)
⚠️ Shared/overloaded database
⚠️ Missing or cold cache
⚠️ Unbounded retries amplifying load
```

## Jebakan

Scale layanan kang bottlenecknya yaiku **database pungkasan** mesthi ngalihake beban luwih akeh menyang DB — scale batasan nyata, dudu gejala.

## Mengapa iku penting

Scale independen ngidini sampeyan gawe kapasitas kanthi tepat nang panggon beban ana, kang luwih murah tinimbang scale monolit sakabehe.

Namun scale buta nyia-nyiain dhuwit lan bisa gawe padhang-padhung; nglakoni pengukuran metrik per-layanan lan trace per-hop yaiku sing kandha batasan nyata kanggo dikempalake.