Why caching improves performance in Express

Introduction

Caching stores data temporarily so your app can get it faster next time. This makes your app quicker and saves work.

When your app fetches the same data many times, like user profiles.

When your app calls slow services or databases repeatedly.

When you want to reduce the load on your server during high traffic.

When you want to speed up page loading for users.

When you want to save bandwidth by not sending the same data again.

Syntax

Express

app.use((req, res, next) => {
  const cachedData = cache.get(req.url);
  if (cachedData) {
    res.send(cachedData);
  } else {
    res.originalSend = res.send.bind(res);
    res.send = (body) => {
      cache.set(req.url, body);
      res.originalSend(body);
    };
    next();
  }
});

This example shows a simple middleware caching responses by URL.

You can use libraries like 'node-cache' or 'redis' for better caching.

Examples

This example caches data for a specific route to avoid repeated database calls.

Express

const cache = new Map();

app.get('/data', (req, res) => {
  if (cache.has('data')) {
    res.send(cache.get('data'));
  } else {
    const data = fetchDataFromDB();
    cache.set('data', data);
    res.send(data);
  }
});

This middleware caches all responses by URL automatically.

Express

app.use((req, res, next) => {
  const cached = cache.get(req.url);
  if (cached) {
    res.send(cached);
  } else {
    res.originalSend = res.send.bind(res);
    res.send = (body) => {
      cache.set(req.url, body);
      res.originalSend(body);
    };
    next();
  }
});

Sample Program

This Express app caches the response for the '/time' route. The first request sends the current time and caches it. Later requests get the cached time instantly, so the time shown does not change until the server restarts.

Express

import express from 'express';

const app = express();
const cache = new Map();

app.use((req, res, next) => {
  const cachedResponse = cache.get(req.url);
  if (cachedResponse) {
    res.send(cachedResponse);
  } else {
    res.originalSend = res.send.bind(res);
    res.send = (body) => {
      cache.set(req.url, body);
      res.originalSend(body);
    };
    next();
  }
});

app.get('/time', (req, res) => {
  const currentTime = new Date().toISOString();
  res.send(`Current time is: ${currentTime}`);
});

app.listen(3000, () => {
  console.log('Server running on http://localhost:3000');
});

Important Notes

Caching can save time but may show old data if not refreshed.

Use cache expiration to keep data fresh.

Test caching carefully to avoid bugs with stale data.

Summary

Caching stores data to speed up repeated requests.

It reduces work for your server and makes apps faster.

Use caching wisely to balance speed and data freshness.

Practice

1. Why does caching improve performance in an Express app?

easy

A. It slows down the server to handle more requests

B. It increases the size of the server's memory permanently

C. It stores data temporarily to avoid repeating expensive operations

D. It deletes old data to free up space immediately

Solution

1. Step 1: Understand caching purpose

   Caching saves results of expensive operations temporarily so they can be reused.

2. Step 2: Relate caching to performance

   By reusing stored data, the server avoids repeating slow tasks, speeding up responses.

3. Final Answer:

   It stores data temporarily to avoid repeating expensive operations -> Option C

4. Quick Check:

   Caching = Temporary storage for speed [OK]

Hint: Caching saves repeated work to speed up responses [OK]

Common Mistakes:

• Thinking caching permanently increases memory
• Believing caching slows down the server
• Confusing caching with deleting data

2. Which Express middleware syntax correctly sets a simple cache header for 1 hour?

easy

A. res.cacheControl('3600')

B. res.set('Cache-Control', 'max-age=3600')

C. res.header('Cache-Control', 'no-cache')

D. res.cache('max-age=3600')

Solution

1. Step 1: Identify correct Express method

   Express uses res.set() or res.header() to set headers; res.set() is common.

2. Step 2: Check cache header format

   'Cache-Control' with 'max-age=3600' sets cache for 3600 seconds (1 hour).

3. Final Answer:

   res.set('Cache-Control', 'max-age=3600') -> Option B

4. Quick Check:

   Correct header syntax = res.set('Cache-Control', 'max-age=3600') [OK]

Hint: Use res.set() with 'Cache-Control' header [OK]

Common Mistakes:

• Using non-existent res.cache() method
• Setting 'no-cache' disables caching
• Wrong method names like res.cacheControl()

3. Consider this Express route with caching logic:

app.get('/data', (req, res) => {
  if (cache.data) {
    res.send(cache.data);
  } else {
    const result = expensiveCalculation();
    cache.data = result;
    res.send(result);
  }
});

What happens on the second request to '/data'?

medium

A. The server sends cached data without recalculating

B. The server runs expensiveCalculation() again

C. The server returns an error because cache.data is undefined

D. The server sends an empty response

Solution

1. Step 1: Analyze first request behavior

   On first request, cache.data is empty, so expensiveCalculation() runs and result is cached.

2. Step 2: Analyze second request behavior

   On second request, cache.data exists, so server sends cached data directly without recalculating.

3. Final Answer:

   The server sends cached data without recalculating -> Option A

4. Quick Check:

   Cache hit = reuse data [OK]

Hint: Cached data skips recalculation on repeat requests [OK]

Common Mistakes:

• Assuming calculation runs every time
• Thinking cache.data is undefined on second request
• Believing server sends empty response

4. This Express caching code has a bug:

app.get('/info', (req, res) => {
  if (cache.info) {
    res.send(cache.info);
  } else {
    const data = fetchData();
    cache.info = data;
    res.send(data);
  }
});

fetchData() is asynchronous and returns a Promise. What is the main issue?

medium

A. fetchData() blocks the server, causing timeout

B. cache.info is never set, causing infinite loop

C. res.send() cannot send strings

D. res.send() is called before fetchData() resolves, sending a Promise object

Solution

1. Step 1: Identify async function usage

   fetchData() returns a Promise but code treats it as synchronous.

2. Step 2: Understand res.send() timing

   res.send(data) runs immediately, sending the unresolved Promise, not actual data.

3. Final Answer:

   res.send() is called before fetchData() resolves, sending a Promise object -> Option D

4. Quick Check:

   Async function needs await before sending [OK]

Hint: Await async calls before sending response [OK]

Common Mistakes:

• Ignoring async nature of fetchData()
• Assuming cache is never set
• Thinking res.send() can't send strings

5. You want to cache user profile data in Express but ensure it updates every 10 minutes. Which approach best balances caching and data freshness?

hard

A. Store data in cache with a timestamp; refresh cache if older than 10 minutes

B. Cache data forever without expiration to maximize speed

C. Never cache user data to always get fresh info

D. Clear cache manually only when server restarts

Solution

1. Step 1: Understand caching with expiration

   To keep data fresh, cache should have a time limit after which it refreshes.

2. Step 2: Evaluate options for freshness and speed

   Store data in cache with a timestamp; refresh cache if older than 10 minutes uses timestamp to refresh cache every 10 minutes, balancing speed and freshness.

3. Final Answer:

   Store data in cache with a timestamp; refresh cache if older than 10 minutes -> Option A

4. Quick Check:

   Timed cache refresh = Store data in cache with a timestamp; refresh cache if older than 10 minutes [OK]

Hint: Use timestamps to refresh cache periodically [OK]

Common Mistakes:

• Caching forever causes stale data
• Never caching loses speed benefits
• Manual cache clearing is unreliable