WebSockets

This lesson covers WebSockets. If this feels new, that is normal. We will build up slowly.

What you will learn

• What websockets 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: Socket.IO — Complete Guide

Explain it simply

WebSockets keep an open connection so server and browser can push messages anytime — unlike normal HTTP request/response.

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

const WebSocket = require('ws');
const wss = new WebSocket.Server({ server });
wss.on('connection', (ws) => {
  ws.on('message', (data) => ws.send('echo: ' + data));
});

Socket.IO wraps WebSockets with fallbacks — often easier for beginners.

What each part does

• const WebSocket = require('ws'); — Loads a built-in module or package you installed with npm.
• const wss = new WebSocket.Server({ server }); — Line 2: runs as written.
• wss.on('connection', (ws) => { — Event pattern: listen with on, trigger with emit.
• ws.on('message', (data) => ws.send('echo: ' + data)); — Event pattern: listen with on, trigger with emit.
• }); — Line 5: runs as written.

Real life: where WebSockets shows up

A support chat widget uses WebSockets 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. websockets-demo.js) in an empty folder
2. Type the example code for WebSockets 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 — WebSockets only feels easy after you run code yourself.

Interview note

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

Summary

• You can explain WebSockets 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