Apa pola publish/subscribe kanggo negara, lan tradeoff-ipun?

Question

Accepted Answer

**Publish/subscribe (pub/sub)** minangka pola messagging ing ngendi **publishers** ngetokake event lan **subscribers** nanggapi, tanpa ngerti siji sama liyane kanthi langsung. Akeh perpustakaan negara (lan sistem event) dibangun ing sadhuwure — toko *ngetokake* pangowahan lan komponen *nandhuji* marang menika.

## Toko pub/sub minimal

```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
    },
  };
}
```

Komponen nyamet `subscribe(callback)` kanggo kanotifikasi; toko nyamet saben subscriber nalika negara owah (`setState`). Iki dhasare carane Redux `store.subscribe`, Zustand, lan event emitter karya ing jero.

## Kauntungan decoupling

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

Coupling sing loose iki marengake bagian sing ora ana hubungane saka app kanggo nanggapi pangowahan sing padha tanpa referensi langsung siji sama liyane — fleksibel lan extensibel.

## Tradeoff-tradeoff

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

Bahaya praktis paling gedhé yaiku **lali unsubscribe** (conto: nalika component unmount), sing bocor memori lan bisa njalari callback murub ing komponen sing mati.

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

## Napa iki penting

Pub/sub minangka **mekanisme root** saka akeh perpustakaan negara lan sistem event — ngerteni iku demystifies carane toko nuduhake komponen lan carane `subscribe`/`unsubscribe` karya.

Iki nerangake loro kekuwatan (komunikasi decoupled, fleksibel) lan bajang (aliran data implisit sing angel dilacak, lan memory leak saka subscription sing ora dibersihke).

Ngenali pub/sub tulung sampeyan nalar babagan reaktivitas ing jero lan nguatake pentinge tansah mbersihke langganan.