Menene bubugar aiki mai bayani/mai ƙarfi bisa ga status, da menene ciniki namu?

Question

Accepted Answer

**Publish/subscribe (pub/sub)** tsari ne na aikin imesaiji inda **masu wallafa** suna aika da abubuwa kuma **masu ƙarfi** suna amsa su, ba tare da sanin juna ba kaikai. Yawancin sigar ƙarfi (da tsarin abubuwa) sun gina a kan shi — ajiye yana aika da canje-canje kuma sassan yana ƙarfe su.

## Ajiye pub/sub rami

```js
function createStore(initial) {
  let state = initial;
  const subscribers = new Set();

return {
    getState: () => state,
    setState(next) {
      state = { ...state, ...next };
      subscribers.forEach((fn) => fn(state)); // PUBLISH: notify all subscribers
    },
    subscribe(fn) {
      subscribers.add(fn);                     // SUBSCRIBE
      return () => subscribers.delete(fn);      // return an unsubscribe function
    },
  };
}
```

Sassan suna karɓa `subscribe(callback)` don sanar; ajiye yana karanta kowane mai ƙarfi lokacin da status ya canja (`setState`). Wannan shine ainihin yadda Redux's `store.subscribe`, Zustand, da abubuwan aiki na aikin gida suke aiki.

## Fa'idar warwar

```text
Publisher (the store) doesn't know WHO is listening.
Subscribers don't know WHO published.
→ They're decoupled, communicating only through the event/store.
```

Dadɗin ɗin wannan sana'a yana ƙiyaye abubuwa na ba da danganta na app su amsa juna canja tabbas ba tare da kai-kai sartakewa ba — sannu da kamushi.

## Ciniki muna

```text
✓ Pros: decoupled, flexible, many-to-many communication, easy to add listeners
✗ Cons:
  - Implicit flow — hard to trace WHO reacts to an event (vs explicit calls)
  - Memory leaks — forgetting to UNSUBSCRIBE keeps dead listeners alive
  - Debugging — indirection makes "why did this run?" harder to answer
  - Ordering — subscriber execution order can be non-obvious
```

Mafi girman haɗari ne **manta wahalar unsubscribe** (misali a sauke ɓangare), wanda ke haifar da zafaren ajiya kuma iya halitta abubuwan aikin a jikin abubuwan matattu.

```jsx
useEffect(() => {
  const unsub = store.subscribe(handleChange);
  return unsub; // ✅ cleanup — unsubscribe on unmount
}, []);
```

## Menene akwai

Pub/sub shine **tsarin asali** na yawancin sigar ƙarfi da tsarin abubuwa — fahimtar shi ya bada shiftin yadda ajiye ke sanar da sassan kuma yadda `subscribe`/`unsubscribe` suke aiki.

Ya koya duka karfi (karɓe, kalmami abubuwan sadarwa) da haɗari (juyayin bayanai jinginar da wuya suwaye, kuma zafaren ajiya daga unsubscribed subscriptions).

Ganin pub/sub yana taimaka maka tunani game da abubuwan gida kuma ya ƙarfafa mahimancin saifi aiki na ƙarshi subscriptions.