Kapan sampeyan ORA kudu nggunakake microservices?

Question

Accepted Answer

Microservices asring minangka pilihan **salah** kanggo miwiti. Peraturan umum yaiku **"monolith dhisik"**: miwiti nganggo monolith sing terstruktur kanthi apik lan ngetokake layanan mung nalika sampeyan duwe alasan sing konkret.

## Ngindhari microservices nalika

```text
✗ Small team — more services than people to run them
✗ Early-stage product — domain boundaries still shifting
✗ No CI/CD, monitoring, or tracing in place
✗ Low traffic — no real scaling pressure
✗ Simple domain — splitting adds cost, not value
```

## Biaya pamisahan sing prematur

Mindhakake panggilan metode in-process menyang panggilan jaringan nambah latency, mode kegagalan, serialisasi, lan unit deployment. Yen watesan salah, sampeyan mbayar kabeh iku **lan** isih kudu refactor liwat layanan.

```text
method call        →  microseconds, can't fail
network call       →  milliseconds, can time out, can be down
```

## Jalur sing luwih apik

```text
Start: modular monolith (clear internal boundaries)
  └─▶ Extract a service ONLY when:
         · it needs independent scaling, OR
         · a separate team needs independent deploys, OR
         · it needs a different tech/SLA
```

## Mengapa iku penting

Kabanyakan tim sing ngasosiasi microservices kawau banget dadi luwih alon, ora luwih cepet, amarga dheweke nggawa beban sistem terdistribusi sadurunge kudu.

Njaga watesan ing monolith dhisik ngidini sampeyan sinau domain kanthi murah lan misah ing jahitan sing bener mengkono.