Why Node.js for server-side JavaScript in Node.js - Performance Evidence

Performance: Why Node.js for server-side JavaScript

HIGH IMPACT

This concept impacts server response time and how quickly the server can handle many requests simultaneously.

Handling multiple client requests on the server

Node.js

import { createServer } from 'http';
import { readFile } from 'fs/promises';
createServer(async (req, res) => {
  // Non-blocking async file read
  const data = await readFile('file.txt');
  res.end(data);
}).listen(3000);

Async file reading allows the event loop to handle other requests while waiting for I/O.

📈 Performance GainNon-blocking I/O improves concurrency and reduces response delays

Handling multiple client requests on the server

Node.js

const http = require('http');
http.createServer((req, res) => {
  // Blocking synchronous file read
  const data = require('fs').readFileSync('file.txt');
  res.end(data);
}).listen(3000);

Using synchronous file reading blocks the event loop, delaying all other requests until the file is read.

📉 Performance CostBlocks event loop, causing high response time and poor concurrency

Performance Comparison

Pattern	Event Loop Blocking	Concurrency	Response Time	Verdict
Synchronous blocking I/O	Blocks event loop	Low concurrency	High response time	[X] Bad
Asynchronous non-blocking I/O	No blocking	High concurrency	Low response time	[OK] Good

Rendering Pipeline

Node.js handles incoming requests using an event loop that processes callbacks without blocking. Non-blocking I/O operations allow the server to continue processing other requests while waiting for slow tasks like file or network access.

→Event Loop

→I/O Operations

→Callback Execution

⚠️ BottleneckBlocking synchronous operations that pause the event loop

Core Web Vital Affected

INP

This concept impacts server response time and how quickly the server can handle many requests simultaneously.

Optimization Tips

1Avoid synchronous blocking calls in Node.js server code.

2Use asynchronous APIs for I/O to keep the event loop free.

3Non-blocking I/O improves server concurrency and response time.

Performance Quiz - 3 Questions

What is the main performance benefit of Node.js using non-blocking I/O?

A It reduces the size of the server code bundle.

B It improves the visual layout of the webpage.

C It allows the server to handle many requests without waiting for slow operations.

D It automatically caches all server responses.

DevTools: Performance

How to check: Record a server profile while sending multiple requests. Look for long blocking tasks in the event loop.

What to look for: Long blocking periods indicate synchronous code slowing down the server; short, quick callbacks show good async usage.

Practice

1. Why is Node.js popular for server-side JavaScript development?

easy

A. It allows using JavaScript on the server for fast and scalable apps

B. It only works with frontend JavaScript

C. It requires a different language for backend

D. It is slower than traditional servers

Solution

1. Step 1: Understand Node.js purpose

   Node.js lets developers use JavaScript on the server side, unlike traditional setups that use other languages.

2. Step 2: Recognize benefits

   This allows building fast and scalable applications using one language for both frontend and backend.

3. Final Answer:

   It allows using JavaScript on the server for fast and scalable apps -> Option A

4. Quick Check:

   Node.js = server-side JavaScript for speed and scale [OK]

Hint: Node.js runs JavaScript on servers for fast apps [OK]

Common Mistakes:

• Thinking Node.js is only for frontend
• Believing Node.js requires multiple languages
• Assuming Node.js is slower than other servers

2. Which of the following is the correct way to import a module in Node.js?

easy

A. import fs from 'fs';

B. using fs;

C. require('fs');

D. include 'fs';

Solution

1. Step 1: Recall Node.js module syntax

   Node.js traditionally uses CommonJS syntax with require() to import modules.

2. Step 2: Identify correct syntax

   The correct way is to call require('fs') to load the file system module.

3. Final Answer:

   require('fs'); -> Option C

4. Quick Check:

   Node.js modules use require() [OK]

Hint: Use require() to import modules in Node.js [OK]

Common Mistakes:

• Using import without enabling ES modules
• Writing include or using which are not valid
• Confusing frontend import syntax with Node.js

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

const http = require('http');
const server = http.createServer((req, res) => {
  res.end('Hello World');
});
server.listen(3000, () => console.log('Server running'));

medium

A. Hello World

B. Server running

C. Error: createServer is not a function

D. Nothing happens

Solution

1. Step 1: Analyze server.listen callback

   The callback passed to server.listen runs when the server starts listening, logging 'Server running'.

2. Step 2: Understand output context

   The console.log prints 'Server running' to the terminal, not the HTTP response.

3. Final Answer:

   Server running -> Option B

4. Quick Check:

   Server start logs 'Server running' [OK]

Hint: Look for console.log inside listen callback for output [OK]

Common Mistakes:

• Confusing console output with HTTP response
• Expecting 'Hello World' in console
• Thinking createServer is undefined

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

const http = require('http');
const server = http.createServer((req, res) => {
  res.write('Hello');
  res.end();
});
server.listen(3000);
console.log('Server running on port 3000');

medium

A. No error, code works correctly

B. res.write should be res.send

C. Missing callback in server.listen

D. res.end() must have a string argument

Solution

1. Step 1: Check server.listen usage

   server.listen can be called without a callback; it still starts the server.

2. Step 2: Verify response methods

   res.write followed by res.end() is valid to send response data in Node.js.

3. Final Answer:

   No error, code works correctly -> Option A

4. Quick Check:

   res.write + res.end() is valid response [OK]

Hint: res.write + res.end() is valid; listen callback optional [OK]

Common Mistakes:

• Thinking res.send exists in Node.js core
• Expecting listen must have callback
• Believing res.end requires argument

5. You want to build a chat app that updates messages instantly for many users. Why is Node.js a good choice for this server-side task?

hard

A. Node.js requires multiple threads for each user connection

B. Node.js cannot handle many simultaneous users

C. Node.js is slower than traditional servers for real-time apps

D. Node.js uses an event-driven model that handles many connections efficiently

Solution

1. Step 1: Understand event-driven model

   Node.js uses an event-driven, non-blocking model that efficiently manages many connections without creating new threads for each.

2. Step 2: Apply to real-time chat app

   This makes Node.js ideal for apps needing instant updates and many simultaneous users, like chat apps.

3. Final Answer:

   Node.js uses an event-driven model that handles many connections efficiently -> Option D

4. Quick Check:

   Event-driven = efficient many users [OK]

Hint: Event-driven model handles many users well [OK]

Common Mistakes:

• Thinking Node.js uses many threads per user
• Assuming Node.js is slow for real-time
• Believing Node.js can't scale for many users