Pub/Sub

This lesson covers Pub/Sub. Think of this lesson as a short workshop you can run on your laptop.

What you will learn

• What pub/sub means — in normal words, not textbook words
• How it works step by step
• Code you can run today on your laptop
• Where teams use this in real projects

Before you start

• Software: Node.js LTS from nodejs.org, VS Code, and a terminal
• Knowledge: Earlier lessons in this Node.js course
• Previous lesson: EventEmitter — Complete Guide

Explain it simply

Publish/subscribe means one part of the app publishes events and other parts subscribe — often through Redis or a message broker.

Why developers use this

• Needed for chat and live data
• Socket.IO simplifies the hard parts
• Fun to demo in interviews

How it works (step by step)

1. Client opens a persistent connection (WebSocket / Socket.IO).
2. Server listens for named events (join, message, typing).
3. Server pushes updates to one user, a room, or everyone.
4. On disconnect, clean up listeners so memory does not leak.

Code example — type this yourself

await redis.publish('orders', JSON.stringify({ id: 1 }));
// another service: redis.subscribe('orders', handler)

Use pub/sub when multiple services need the same event without direct calls.

What each part does

• await redis.publish('orders', JSON.stringify({ id: 1 })); — Async work — Node can serve other users while this waits.
• // another service: redis.subscribe('orders', handler) — Line 2: runs as written.

Real life: where Pub/Sub shows up

A support chat widget uses Pub/Sub so when an agent replies, the customer sees it instantly — no refresh button. In interviews, explain the trade-off you chose and what you would measure in production.

Try it yourself — hands-on

1. Create a new file (e.g. pub-sub-demo.js) in an empty folder
2. Type the example code for Pub/Sub yourself — typing helps memory
3. Run node on that file and read the output
4. Change one line (a value, a message, a route path) and run again to see what breaks or improves

Common mistakes (avoid these)

• Skipping the terminal — Pub/Sub only feels easy after you run code yourself.

Interview note

Senior interviews may ask how Pub/Sub behaves under load, failure, or security review — mention logging, timeouts, and validation.

Summary

• You can explain Pub/Sub in your own words
• You ran working code — not just read about it
• You know one mistake to avoid and one real place teams use this