Why async patterns are critical in Node.js in Node.js - See It in Action

Why async patterns are critical in Node.js

📖 Scenario: You are building a simple Node.js server that handles multiple user requests. Each request needs to read a file and then send the content back to the user.Without async patterns, the server would wait for one file read to finish before starting the next. This causes delays and poor user experience.

🎯 Goal: Learn how to use asynchronous patterns in Node.js to handle multiple file reads efficiently without blocking the server.

📋 What You'll Learn

Create a function to read a file asynchronously using fs.promises.readFile

Create a helper variable to hold the file path

Use async and await to read the file content

Add a simple server response that sends the file content back

💡 Why This Matters

🌍 Real World

Web servers often need to handle many user requests at once. Using async patterns lets servers read files, query databases, or call APIs without waiting and blocking other users.

💼 Career

Understanding async patterns in Node.js is essential for backend developers to build fast, scalable, and responsive web applications.

1

DATA SETUP: Import fs/promises and create a file path variable

Write code to import fs/promises as fs and create a variable called filePath with the value './data.txt'.

Node.js

import fs from 'fs/promises';
// Your code here

Hint

Use import fs from 'fs/promises' to get the promise-based file system methods.

Create filePath as a constant string './data.txt'.

2

CONFIGURATION: Create an async function to read the file

Write an async function called readFileContent that takes no parameters.

Node.js

import fs from 'fs/promises';
const filePath = './data.txt';

// Your code here

Hint

Define an async function named readFileContent with empty body for now.

3

CORE LOGIC: Use await to read the file content inside the async function

Inside the readFileContent function, use await fs.readFile(filePath, 'utf-8') to read the file content and store it in a variable called content. Then return content.

Node.js

import fs from 'fs/promises';
const filePath = './data.txt';

async function readFileContent() {
    // Your code here
}

Hint

Use await to wait for the file read to finish without blocking.

Return the file content so it can be used later.

4

COMPLETION: Create a simple server that uses the async function and sends the file content as response

Import http from 'node:http'. Create a server using http.createServer that calls readFileContent() and sends the content as the response with status code 200. Listen on port 3000.

Node.js

import fs from 'fs/promises';
const filePath = './data.txt';

async function readFileContent() {
    const content = await fs.readFile(filePath, 'utf-8');
    return content;
}

// Your code here

Hint

Use http.createServer with an async callback to handle requests.

Call readFileContent() with await to get the file content.

Send the content with res.end() and set status 200.

Listen on port 3000 to accept connections.

Practice

1. Why are async patterns important in Node.js?

easy

A. They are only needed for database connections.

B. They make the code run slower but more securely.

C. They allow Node.js to use multiple CPU cores automatically.

D. They prevent blocking the main thread, keeping the app responsive.

Solution

1. Step 1: Understand Node.js single-thread model

   Node.js runs on a single main thread, so blocking operations freeze the app.

2. Step 2: Role of async patterns

   Async patterns let Node.js handle tasks without waiting, keeping it responsive.

3. Final Answer:

   They prevent blocking the main thread, keeping the app responsive. -> Option D

4. Quick Check:

   Async = Non-blocking main thread [OK]

Hint: Async avoids freezing by not blocking main thread [OK]

Common Mistakes:

• Thinking async makes code slower
• Believing Node.js uses multiple cores automatically
• Assuming async is only for databases

2. Which of the following is the correct syntax to declare an async function in Node.js?

easy

A. async function myFunc() {}

B. async myFunc function() {}

C. function myFunc async() {}

D. function async myFunc() {}

Solution

1. Step 1: Recall async function syntax

   The correct syntax places async before the function keyword.

2. Step 2: Check each option

   Only async function myFunc() {} correctly writes async function myFunc() {}.

3. Final Answer:

   async function myFunc() {} -> Option A

4. Quick Check:

   async before function keyword [OK]

Hint: Put async before function keyword [OK]

Common Mistakes:

• Placing async after function name
• Using async inside parentheses
• Mixing order of async and function

3. What will the following Node.js code output?

async function fetchData() {
  return 'data';
}

fetchData().then(console.log);
console.log('start');

medium

A. data\nstart

B. start

C. start\ndata

D. data

Solution

1. Step 1: Understand async function return

   Async functions return a promise resolved with the value 'data'.

2. Step 2: Execution order of promises and console.log

   console.log('start') runs immediately, then the promise resolves and logs 'data'.

3. Final Answer:

   start\ndata -> Option C

4. Quick Check:

   Sync logs before async promise [OK]

Hint: Sync logs print before async promise resolves [OK]

Common Mistakes:

• Assuming async return logs immediately
• Thinking promise blocks next line
• Confusing order of console.log calls

4. Identify the error in this Node.js async code snippet:

async function readFile() {
  const data = fs.readFileSync('file.txt');
  console.log(data);
}

medium

A. Missing await keyword before fs.readFileSync call.

B. Using synchronous readFileSync inside async function blocks event loop.

C. fs.readFileSync does not exist in Node.js.

D. Async functions cannot use console.log.

Solution

1. Step 1: Check usage of fs.readFileSync

   readFileSync is synchronous and blocks the event loop, which is bad in async functions.

2. Step 2: Understand async function best practices

   Async functions should use non-blocking calls like fs.promises.readFile with await.

3. Final Answer:

   Using synchronous readFileSync inside async function blocks event loop. -> Option B

4. Quick Check:

   Sync calls block event loop in async code [OK]

Hint: Avoid sync calls inside async functions [OK]

Common Mistakes:

• Thinking await works with sync functions
• Believing readFileSync is async
• Assuming console.log is disallowed in async

5. You want to fetch data from two APIs in Node.js and combine results. Which async pattern best ensures both calls run at the same time and you wait for both results before continuing?

hard

A. Use Promise.all with both API calls and await the combined promise.

B. Call both APIs without await and process results immediately.

C. Call one API, await it, then call the second API and await it.

D. Use setTimeout to delay the second API call after the first.

Solution

1. Step 1: Understand sequential vs parallel calls

   Awaiting one API before calling the second runs them sequentially, slowing total time.

2. Step 2: Use Promise.all for parallel execution

   Promise.all runs both calls simultaneously and waits for both to finish before continuing.

3. Final Answer:

   Use Promise.all with both API calls and await the combined promise. -> Option A

4. Quick Check:

   Promise.all runs async calls in parallel [OK]

Hint: Use Promise.all to await multiple async calls together [OK]

Common Mistakes:

• Running calls sequentially causing delays
• Not awaiting promises causing undefined results
• Using setTimeout for async control