SSE

This lesson covers SSE. Here is the idea in simple words, then we write real code.

What you will learn

• What sse 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: WebSockets — Complete Guide

Explain it simply

Server-Sent Events (SSE) let the server push text updates to the browser over one long HTTP connection.

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

app.get('/events', (req, res) => {
  res.setHeader('Content-Type', 'text/event-stream');
  res.write('data: hello\n\n');
});

Good for live feeds and AI token streaming. One-way: server to client only.

What each part does

• app.get('/events', (req, res) => { — Defines what happens when a client hits this URL and HTTP method.
• res.setHeader('Content-Type', 'text/event-stream'); — Line 2: runs as written.
• res.write('data: hello\n\n'); — Line 3: runs as written.
• }); — Line 4: runs as written.

Real life: where SSE shows up

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

Interview note

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

Summary

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