Mene ne bambanci tsakanin EventEmitter da job queue a Node.js?

Question

IT Interview Practice · Accepted Answer

Zaɓi tsakanin EventEmitter da job queue ta tambayar **inda aikin dole ya gudana da abin da zai faru idan process ya tsaya**.

EventEmitter yana sanar da listeners a cikin Node.js process ɗaya. Durable queue tana adana aiki don workers su sarrafa daga baya. Dukansu suna raba nauyin aiki, amma halinsu idan failure ya faru ya bambanta.

## 1. Bi sanarwar local

A ce component ya gama initialization kuma yana son sauran components a process ɗin su mayar da martani. EventEmitter ya dace: rajista listeners, sannan emit event.

```text
[One process]
emit("ready") -> Listener A
              -> Listener B
```

Node.js yana kiran listeners synchronously bisa tsarin rajistarsu. Ba a adana event ga wanda zai yi rajista daga baya ba, kuma aikin da bai kammala ba ba ya tsira bayan crash. [Node.js Events](https://nodejs.org/api/events.html).

Wannan ya dace idan sanarwar local ce kuma ana iya rasa ta ko sake gina ta. Bai isa ba idan kasuwanci yana sa ran aikin ya tsira bayan sender ya tsaya.

## 2. Fahimci abin da async listener yake canzawa

Async listener zai iya fara asynchronous work, amma emit ba ya jiran promise da ya dawo. Don haka tsarin kiran listeners ba lallai ya zama tsarin kammalawarsu ba.

Synchronous code mai nauyin CPU a cikin listener har yanzu yana jinkirta process. Kula da thrown errors da rejected promises da gangan; captureRejections zai iya kai rejections zuwa error handling, amma ba ya adana ko retry task.

Ƙara async yana sauya yadda listener yake aiki. Ba ya mayar da event na memory zuwa durable queue.

## 3. Bi task da aka saka queue

Yanzu a ce adana oda dole ya kai ga ƙirƙirar invoice a ƙarshe. Queue tana samar da wurin riƙe umarnin yayin da workers ba sa nan ko suna da aiki.

```text
[Producer] -> [Durable queue] -> [Available worker]
                    |                   |
              [Pending work]      [Result / retry]
```

Producer yana tura job; worker yana sarrafa attempt kuma ya rubuta sakamako. Ana iya deploy da scale workers daban da API. Durability har yanzu ya dogara da storage da configuration na queue.

A queue mai competing workers ta yau da kullum, worker ɗaya yana sarrafa kowace attempt. Wannan ya bambanta da aika event ga duk EventEmitter listeners. Idan independent subscribers da yawa suna bukatar event ɗin, zaɓi ko saita delivery model da ke tallafa wa wannan buƙata.

## 4. Bincika gibin tsakanin adanawa da enqueue

Da EventEmitter, crash bayan adana oda amma kafin emit zai iya rasa umarnin invoice. Durable queue tana kare job bayan ta karɓe shi, amma ba ta kare gibin da ke tsakanin database commit da submission kai tsaye ba.

Outbox yana rufe gibin ta adana oda da umarninta a transaction ɗaya. Publisher yana karanta outbox kuma ya aika job daga baya.

Delivery zai iya maimaituwa idan publisher ya rasa confirmation. Ba wa ƙirƙirar invoice stable business key da uniqueness constraint ko wata idempotent implementation. Sake attempt bai kamata ya ƙirƙiri invoice na biyu ba. [Idempotent jobs](https://docs.bullmq.io/patterns/idempotent-jobs).

## 5. Kwatanta zaɓuɓɓuka da buƙatar gaske

| Buƙata | EventEmitter | Durable job queue |
| --- | --- | --- |
| Sanar da components a process ɗaya | Kai tsaye kuma marar nauyi | Yawanci yana ƙara infrastructure marar buƙata. |
| Riƙe pending work bayan sender ya tsaya | Babu durable record a ciki | Mai yiwuwa da storage da recovery masu dacewa. |
| Retry da binciken backlog | Application dole ya gina wannan | Abubuwan queue na gama gari, tare da configuration. |
| Gudanar da aiki a wasu machines | Ba aikinsa ba ne | Workers suna iya gudana daban. |

Ga initialization, zan yi amfani da EventEmitter. Ga invoice generation da dole ya farfaɗo daga failure, zan yi amfani da durable queue kuma in tsara database handoff da duplicate attempts.

Gwada ta dakatar da process a iyakoki masu muhimmanci: kafin submission, bayan acceptance da bayan business effect. Sakamakon ya dace da tabbacin da mai amfani yake tsammani.

**Ka tuna:** local notification → EventEmitter; background work mai recovery → durable queue. Ga tasiri mai muhimmanci, tsara handoff da idempotency ma.

Buƙata	EventEmitter	Durable job queue
Sanar da components a process ɗaya	Kai tsaye kuma marar nauyi	Yawanci yana ƙara infrastructure marar buƙata.
Riƙe pending work bayan sender ya tsaya	Babu durable record a ciki	Mai yiwuwa da storage da recovery masu dacewa.
Retry da binciken backlog	Application dole ya gina wannan	Abubuwan queue na gama gari, tare da configuration.
Gudanar da aiki a wasu machines	Ba aikinsa ba ne	Workers suna iya gudana daban.

1. Bi sanarwar local

2. Fahimci abin da async listener yake canzawa

3. Bi task da aka saka queue

4. Bincika gibin tsakanin adanawa da enqueue

5. Kwatanta zaɓuɓɓuka da buƙatar gaske

Tambayoyi masu alaƙa