Menene publisher confirms a cikin RabbitMQ?

Question

Accepted Answer

**Publisher confirms** su ne tsarin da RabbitMQ ke bakin cikakken sanarwa ga mai sadarwa cewa ya karba (kuma ya ajiye) sakin — tabbatar da cewa sakunan ba za su ɓata a gefen aiki ba. Suna da alhakin gida ga bakin mai amsa gaida ɗin mai karba.

## Matsalar: sannu sakin ya isa ga broker?

```text
When a producer publishes a message, by default it doesn't KNOW if RabbitMQ received it:
  → network failure, broker issue → the message could be LOST without the producer knowing
  → for reliability, the producer needs CONFIRMATION that the message was accepted
→ publisher confirms address the PUBLISHING side of reliability
```

## Yadda publisher confirms ke aiki

```text
PUBLISHER CONFIRMS → the broker sends an ACK back to the producer for each message:
  → enable confirm mode on the channel
  → the broker ACKs a message once it has taken responsibility (received it; for persistent
    messages on durable queues → once persisted to disk)
  → NACK → the broker couldn't handle the message (the producer can retry)
→ the producer KNOWS each message was accepted (or not) → no silent loss
```

## Amfani da confirms

```text
✓ Wait for confirms (sync) → simple but slower; or handle confirms ASYNCHRONOUSLY (callbacks)
  for throughput (don't block on each)
✓ Batch confirms → confirm batches for better throughput
✓ On NACK/timeout → retry the message (with idempotency awareness)
→ combine with durable queues + persistent messages → reliable end-to-end publishing
```

## Me ya sa hakan muhimmi

Tuntunin publisher confirms yana da mahimmanci saboda suna da **mahimmanci don ingancin sadarwa na aiki a RabbitMQ**, don haka ilimi mai mahimmanci ne don gina sadarwon sakin da amintacce.

Publisher confirms suna daidaita wata babbar buɓe-buɓe na ingancin: kafin a sake, idan mai aiki ya buga sakin, ba ya san akwai halin RabbitMQ a halaka kawo gareshinsa, don haka kuskure na hanyar sadarwa ko matsalar broker na iya **watse sakin ba tare da sanin mai aiki** — matsalar ingancin gaske a gefen sadarwa.

Tuntunin **yadda publisher confirms ke aiki** — broker yana aika **ack baya ga mai aiki** ga kowane sakin da zarai ya dauki alhakin (karowar, ko don abubbuwan da ke zama jiya a jigon takaici, da zarai aka ajiye a rediski), tare da **nack** idan broker ba zai iya hakin shi (don haka mai aiki zai iya yada kawo) — yana bayyyana tsarin da ke ba mai aiki tabbatarwa, hana surutu sakin asiri a sadarwa.

Wannan shi ne **alhakin gefen mai aiki zuwa bakin ba shi amsa ɗin mai karba** (wanda ke karewa gefe na amfani), tare da jama'a saida cewa akwai inganci-buɗe.

Tuntunin **amfani da confirms** — jira don confirms ta hanyar daidaitacce (sai a gida amma a sannu) zuwa halin asalin su ta hanyar callbacks (don yaduwar), jujjuya confirms, da yada kawo akan nack/timeout (tare da ilimin sauran-bata) — yana nuna amfani mai gida, mai inganci.

Tuntunin cewa haɗa publisher confirms tare da gidajiya takaici da sakunan da ke zama jiya tabbatarwa saida cewa aiki-buɗe-buɗe safiya yana haɗa confirms zuwa babbar hotuna ta inganci (confirms don gefen sadarwa, takaici don ajiyewa, acks don amfani).

Publisher confirms suna da mahimmanci don tabbatar da cewa sakunan suna amintaccen zuwa broker, wani mahimmin bangare na sadarwon sakin da aka ƙoƙari (jama'a suna mai da hankali akan bakin ba shi amsa ɗin kai amma suna manta da ingancin gefen sadarwa).

Tun da publisher confirms suna da mahimmanci don ingancin sadarwa na aiki (tabbatar da cewa sakunan suna kai ga broker, hana surutu asiri) — alhakin gefen mai aiki zuwa bakin ba shi amsa ɗin — kuma haɗar su mahimmi ce don sadarwon sakin inganci-buɗe-buɗe, haɗar publisher confirms yana da muhimmanci, gida-gida-zahiri RabbitMQ ilimi — mahimmi don ingancin sadarwa na aiki (hana asiriyar sakin watse a sadarwa), kammala hotuna inganci tare da bakin ba shi amsa ɗin asalin gida kuma mahimmi don gina RabbitMQ tsarin inganci tare da cikakken baye wajajji.