Response time optimization in Node.js - Step-by-Step Execution

Concept Flow - Response time optimization

Request Received

↓

Check Cache

↓

Return Cache

↓

Fetch Data / Compute

↓

Store in Cache

↓

Send Response

↓

End

This flow shows how a server can optimize response time by checking cache first, then processing only if needed.

Execution Sample

Node.js

import http from 'node:http';
const cache = new Map();
http.createServer((req, res) => {
  if (cache.has(req.url)) {
    res.end(cache.get(req.url));
  } else {
    const data = 'Response for ' + req.url;
    cache.set(req.url, data);
    res.end(data);
  }
}).listen(3000);

A simple Node.js server that caches responses to reduce processing time on repeated requests.

Execution Table

Step	Request URL	Cache Check	Cache Hit?	Action	Response Sent
1	/home	cache.has('/home')	No	Compute response, store in cache	Response for /home
2	/home	cache.has('/home')	Yes	Return cached response	Response for /home
3	/about	cache.has('/about')	No	Compute response, store in cache	Response for /about
4	/home	cache.has('/home')	Yes	Return cached response	Response for /home
5	/about	cache.has('/about')	Yes	Return cached response	Response for /about

💡 Server keeps running; each request checks cache and responds accordingly.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 5
cache	{}	{'/home': 'Response for /home'}	{'/home': 'Response for /home', '/about': 'Response for /about'}	{'/home': 'Response for /home', '/about': 'Response for /about'}

Key Moments - 2 Insights

Why does the server check the cache before processing the request?

Checking the cache first (see execution_table steps 2 and 4) avoids recomputing the response, saving time and resources.

What happens if the requested URL is not in the cache?

The server computes the response, stores it in the cache (steps 1 and 3), then sends it to the client.

Visual Quiz - 3 Questions

Look at the execution table, what is the response sent at step 3?

A Response for /about

B Response for /home

C No response sent

D Error message

💡 Hint

Check the 'Response Sent' column for step 3 in the execution_table.

At which step does the cache first contain the '/about' URL?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the variable_tracker for cache contents after each step.

If the cache was empty and the first request was '/contact', what would happen at step 1?

A Return cached response

B Compute response and store in cache

C Send error response

D Ignore the request

💡 Hint

Refer to the action taken when cache.has(req.url) is false in the execution_table.

Concept Snapshot

Response time optimization in Node.js:
- Use a cache (e.g., Map) to store responses.
- On request, check cache first.
- If cached, return immediately.
- If not, compute response, store it, then return.
- This reduces repeated processing and speeds up responses.

Full Transcript

This example shows how a Node.js server can optimize response time by using a cache. When a request comes in, the server first checks if the response is already stored in the cache. If yes, it returns the cached response immediately, saving time. If not, it computes the response, stores it in the cache for future requests, and then sends it. The execution table traces multiple requests showing cache hits and misses. The variable tracker shows how the cache grows with each new URL. Key moments clarify why checking the cache first is important and what happens when a URL is not cached. The quiz tests understanding of cache hits, cache updates, and response actions. This approach helps servers respond faster by avoiding repeated work.