Async Iterators

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

What you will learn

• What async iterators 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: Buffers — Complete Guide

Explain it simply

Async iterators let you loop over data that arrives over time — like lines from a file or messages from a queue — with for await.

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

async function printLines(stream) {
  for await (const line of stream) {
    console.log(line);
  }
}

Readable streams can be async iterable in modern Node. Handy for clean loop syntax over async sources.

What each part does

• async function printLines(stream) { — Async work — Node can serve other users while this waits.
• for await (const line of stream) { — Async work — Node can serve other users while this waits.
• console.log(line); — Prints to the terminal — great for learning; use proper logging in production.
• } — Line 4: runs as written.
• } — Line 5: runs as written.

Real life: where Async Iterators shows up

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

Interview note

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

Summary

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