Mikro-huduma ya event-driven architecture ni nini?

Question

Accepted Answer

Katika **architectu ya event-driven**, huduma zinarudia kwa **kuzalisha na kula matukio** kupitia broker (Kafka, RabbitMQ, n.k.). Huduma inatangaza kwamba kitu kilichotokea; huduma zenye nia zinarejelea — mzalishi hajui au hasubiri.

## Jinsi inavyofanya kazi

```text
Order Service ─publish→ [ Event Broker: "order.placed" ]
                              │
            ┌─────────────────┼──────────────────┐
            ▼                 ▼                  ▼
      Inventory         Notification          Analytics
      (reserve stock)   (send email)          (record metric)
```

## Mfano wa event payload

```json
{
  "eventType": "order.placed",
  "eventId": "e-9f2c",          // unique → consumers dedupe
  "occurredAt": "2026-06-18T10:00:00Z",
  "data": { "orderId": "42", "total": 99.5 }
}
```

## Faida

- **Miunganisho iliyobonyeza** — ongeza mtumiaji mpya bila kubadilisha mzalishi.
- **Kuzingatiwa** — broker inabuffer matukio wakati wa vunjiko.
- **Scalability** — watumiaji wanakua kwa kujitegemea.

## Mitego

```text
⚠️ Eventual consistency — readers may briefly see stale data
⚠️ Duplicate delivery — make consumers idempotent (use eventId)
⚠️ Ordering — only guaranteed within a partition/queue
⚠️ Hard to trace a flow across many consumers
```

## Kwa nini ni muhimu

Jiometri ya event-driven ni kile kinachokukuwezesha kuongeza uwezo (uchambuzi, ukaguzi wa ulaghai, arifa) kwa kusanidi tu, bila mabadiliko yoyote kwa mizalishi iliyopo.

Uwezo huu wa kupanua na kuzingatiwa unakuja kwa bei ya uwiano wa mwisho na debugging ngumu — compromise ya kati ambayo unakubali wakati unakokwenda event-driven.