Buffers

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

What you will learn

• What buffers 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: Streams — Complete Guide

Explain it simply

A Buffer is raw binary data in Node — bytes from a file, network packet, or image before you turn it into a string.

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 buf = Buffer.from('Hello');
console.log(buf.toString('utf8'));
console.log(buf.length);

Use utf8 when converting text. Binary uploads often stay as Buffers until you save them.

What each part does

• const buf = Buffer.from('Hello'); — Line 1: runs as written.
• console.log(buf.toString('utf8')); — Prints to the terminal — great for learning; use proper logging in production.
• console.log(buf.length); — Prints to the terminal — great for learning; use proper logging in production.

Real life: where Buffers shows up

An online store uses Buffers 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. buffers-demo.js) in an empty folder
2. Type the example code for Buffers 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 — Buffers only feels easy after you run code yourself.

Interview note

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

Summary

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