Streams

This lesson covers Streams. Let us learn this step by step — no rush, no jargon first.

What you will learn

• What streams 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: Timers — Complete Guide

Explain it simply

Streams read or write data in chunks instead of loading everything into memory. Great for large files and video.

Why developers use this

• Node stays fast under load
• Required for files and databases
• Common in interviews

How it works (step by step)

1. Your code starts a task (read file, query DB, timer).
2. Node continues other work instead of waiting idle.
3. When the task finishes, your callback, Promise, or await runs.
4. Errors go in catch or .catch() — never ignore them.

Code example — type this yourself

const fs = require('fs');
const read = fs.createReadStream('package.json');
read.on('data', (chunk) => console.log('chunk', chunk.length));
read.on('end', () => console.log('done'));

Each data event is a piece of the file. Piping streams together is common: readStream.pipe(writeStream).

What each part does

• const fs = require('fs'); — Loads a built-in module or package you installed with npm.
• const read = fs.createReadStream('package.json'); — Line 2: runs as written.
• read.on('data', (chunk) => console.log('chunk', chunk.length)); — Event pattern: listen with on, trigger with emit.
• read.on('end', () => console.log('done')); — Event pattern: listen with on, trigger with emit.

Real life: where Streams shows up

An online store uses Streams so hundreds of users can check order status at once. While one request waits for the database, Node handles other users instead of freezing. Start small: one feature working beats a perfect architecture on paper.

Try it yourself — hands-on

1. Create a new file (e.g. streams-demo.js) in an empty folder
2. Type the example code for Streams 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 — Streams only feels easy after you run code yourself.

Interview note

Interviewers often ask: “What is Streams?” Answer in one sentence, then give a tiny example you actually ran.

Summary

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