X'inhi l-arkitettura driven-by-events fil-microservices?

Question

Accepted Answer

F'**arkitettura driven-by-events**, is-servizzi jikkomunikaw billi **jiprodumu u jikkunsmaw events** permezz ta' broker (Kafka, RabbitMQ, eċċ.). Servizz jannunzja li xi ħaġa ġrat; is-servizzi interessati jirreaġixxu — il-produttur ma jafx u ma jistennax għalihom.

## Kif taħdem

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

## Eżempju tal-payload tal-event

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

## Benefizzi

- **Coupling baxx** — żid konsumer ġdid mingħajr ma tintokka l-produttur.
- **Resilienza** — il-broker ibuffra l-events matul ħames.
- **Skalabilità** — il-konsumers jiskaljaaw b'mod indipendenti.

## Pitfalls

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

## Għaliex importanti

It-tqassim driven-by-events huwa dak li jhallik tżid kapabilities (analytics, fraud checks, notifikazzjonijiet) billi sempliċement tisoskrivixxi, bla ebda bidliet għal produtturi eżistenti.

Dik l-estensibilità u resilienza ġejjin bil-prezzju ta' eventual consistency u debugging aktar diffiċli — il-kunflitt ċentrali li taċċetta meta tmur event-driven.