Menene event-driven architecture a cikin microservices?

Question

Accepted Answer

A cikin **event-driven architecture**, ayyukan suna sadarwa ta hanyar **samarwa da cinye abubuwan da suka faru** ta wata makamashin (Kafka, RabbitMQ, da sauransu). Wani aiki ya sanar cewa wani abin ya faru; ayyukan da ke da sha'awa suna amsawa — mai samarwa bai sani ba ko jira musu.

## Yadda yake aiki

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

## Misalin nau'in abin da aka samarwa

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

## Fa'idodi

- **Kuncin haɗi ba ya da nauyi** — ƙara mai cinye sabbin ba tare da taɓawa mai samarwa ba.
- **Karfin miƙa** — makamashin yana adana abubuwan da suka faru yayin haɗari.
- **Ƙarfin yunƙuri** — masu cinye suna ƙarfafa kansu.

## Abubuwan da ake ciki

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

## Dalilin da ya sa ya matuwa

Sayen event-driven shine abin da ke ba ka damar samun ƙarfi (nazari, bincike na ruɗani, sanarwa) ta hanyar sha'awata kawai, ba tare da canja zuwa mai samarwa na jiya ba.

Wancan warewa da karfin miƙa sun zo ne a farashi na ƙarfin da ɗaya da wahala a neman kurakurai — matsalar da ke tsakiya da ke hade ma ka tuna lokacin da ka tafi event-driven.