Lini unapaswa kutumia microservices?

Question

Accepted Answer

Microservices mara nyingi ni **chaguo lisilo sahihi** mwanzoni. Sheria ya kawaida ni **"monolith first"**: anza na monolith iliyotengenezwa vizuri na uondoe huduma tu wakati una sababu ya halisi.

## Epuka microservices wakati

```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
```

## Gharama ya mgawanyiko mapema

Kuhamisha wito wa njia (in-process method call) kwenye wito wa mtandao kunaongeza kuchelewa, njia za kushindwa, uondoaji wa serial, na kitengo cha usambazaji. Ikiwa mipaka ni vibaya, hulipwa hii yote **na** bado lazima isanifue upya katika huduma.

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

## Njia bora

```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
```

## Kwa nini inamaanisha

Timu nyingi zinazozikubali microservices mapema huishia polepole, si haraka, kwa sababu zinachukua juu ya mzigo wa mifumo iliyosambazwa kabla ya kuhitaji.

Kuzuia mipaka ndani ya monolith kwanza hukuruhusu kujifunza kikoa kwa bei nafuu na kugawanya kwenye miondo sahihi baadaye.