Apa iku skalabilitas lan paano carane makamit?

Question

Accepted Answer

**Skalabilitas** yaiku kemampuan sistem kanggo **nangani beban sing tambah** (luwih akeh pengguna, panjaluk, data) kanthi nambah sumber daya. Makamit kanthi **vertical scaling** (mesin sing luwih gedhe) lan utamane **horizontal scaling** (luwih akeh mesin), bebarengan karo teknik kayata load balancing, caching, lan distribusi.

## Apa iku skalabilitas

```text
SCALABILITY = the ability to handle GROWTH (more load) by adding resources, maintaining
performance:
  → a scalable system handles 10x or 100x the load by adding capacity
  → a non-scalable system degrades/fails as load grows (a bottleneck)
→ essential because successful systems grow.
```

## Vertical vs horizontal scaling

```text
VERTICAL (scale UP) → a BIGGER machine (more CPU, RAM):
  ✓ simple (no app changes)  ✗ LIMITS (max machine size); expensive; single point of
    failure; downtime to upgrade
HORIZONTAL (scale OUT) → MORE machines (add servers; distribute load):
  ✓ scales nearly unlimited; redundancy/fault tolerance; the approach for large scale
  ✗ more complex (distributed system; need load balancing, statelessness, data distribution)
→ Horizontal scaling is key for large-scale systems (add commodity machines vs one giant one).
```

## Teknik kanggo scaling

```text
✓ LOAD BALANCING → distribute requests across multiple servers (enables horizontal scaling)
✓ STATELESS services → so any server can handle any request (essential for horizontal scaling)
✓ CACHING → reduce load on databases/backends (serve from fast cache)
✓ DATABASE scaling → replication (read scaling), sharding (split data), caching
✓ ASYNC processing / queues → handle work without blocking; absorb spikes
✓ CDN → distribute static content; microservices → scale parts independently
```

## Mengapa iku penting

Pamahaman babagan skalabilitas dadi dhasar amarga **nangani pertumbuhan yaiku syarat inti kanggo sistem sing sukses**, lan skalabilitas dadi pusat ing system design, mula menawa keluwihen ilmu.

Skalabilitas — nangani beban sing tambah kanthi nambah sumber daya nalika tetap jaga performa — menawa penting amarga sistem sing sukses bakal tuwuh (luwih akeh pengguna, traffic, data), lan sistem sing ora bisa scale bakal rusak utawa gagal bilih ana bottleneck.

Pamahaman babagan **pédésan vertical vs horizontal scaling** dadi inti: vertical scaling (mesin sing luwih gedhe) gampang nanging duwe wates (ukuran mesin maksimal, biaya, titik kegagalan tunggal), dene **horizontal scaling** (luwih akeh mesin) bisa scale nearpak tanpa batas kanthi redundansi nanging merlokake kerumitan distributed-systems (load balancing, statelessness, distribusi data).

Pamahaman manawa **horizontal scaling dadi kunci kanggo sistem skala gedhe** (nambah mesin komoditas tinimbang siji mesin raksasa) yaiku konsep system-design inti.

Pamahaman babagan **teknik-teknik** — **load balancing** (ngalokasi panjaluk, ngaktifake horizontal scaling), **stateless services** (mula saben server nangani saben panjaluk, penting kanggo horizontal scaling), **caching** (nyuda beban backend), **database scaling** (replication, sharding), **async processing/queues** (nanggepe spike), lan CDN lan microservices — menehi perangkat kanggo ngwangun sistem scalable.

Teknik-teknik iki bakal ketemu maneh ing system design.

Amarga nangani pertumbuhan yaiku syarat inti lan skalabilitas (utamane horizontal scaling karo teknik panjurunge) yaiku carane sistem nangani beban sing tambah, lan amarga pamahaman babagan pendekatan scaling lan teknik-teknik dadi dhasar ing system design, pemahaman skalabilitas yaiku kaluwihen ilmu dhasar system-design — pusat ing ngwangun sistem kanggo nangani pertumbuhan, kepedulian inti ing nearpak kabeh system design, lan dhasar kanggo ngerti paano sistem skala gedhe dibangun kanggo nangani beban raksasa.