Menene ƙa'idar "database-per-service"?

Question

Accepted Answer

**Database per service** yana nufin cewa kowane microservice yana da kansa kanta bakin data mai sirrˈi, kuma babu wani sabis da zai iya karantawa ko rubuta shi kai tsaye. Sauran sabis dole ne su je ta API na sabis mai kula.

## Me ya sa haka mahimmanci

```text
┌──────────┐     ┌──────────┐     ┌──────────┐
│  Orders  │     │ Payments │     │  Users   │
│ service  │     │ service  │     │ service  │
└────┬─────┘     └────┬─────┘     └────┬─────┘
     ▼                ▼                ▼
  ordersDB        paymentsDB        usersDB   ← private, no cross-access
```

Idan Orders yana buƙatar bakin bayanan mai amfani, zai kira API Users — baya **ba** shi yana bugun tambaya `usersDB` kai tsaye.

## Me ya sa a ɓoye shi

- **Loose coupling** — sabis iya canza skemansa kyauri.
- **Independent deployment** — babu mikirista ɗa aka raba-schema a gida na gabas.
- **Technology choice** — sabis ɗaya yana amfani da Postgres, wani yana amfani da MongoDB.

## Farashin

```text
With no shared DB:
  ✗ no cross-service JOINs
  ✗ no single ACID transaction across services
  → need API composition, replication, or sagas instead
```

## Damici

**Bakin data ɗa aka raba** shine alamu na anti-pattern gida — yana damice sabis kyauri don kada su iya amfani kai tsaye.

## Me ya sa haka mahimmanci

Bakin bayanan mai sirrˈi ne kawai abubuwan da suke shi aiki sabis na gida; raba bakin data kuma kuna da monolith ɗa aka raba.

Farashin shine cewa haɗi da abubuwan juna yanzu yana yaɗuwa a sabis, wanda ke tilasta alamu kamar sagas da daidaitacciyar rashin tsattsauran ajya — wacce ta a da yarda asirin ga 'yancin sarari.