Why caching improves performance in Express - Performance Evidence

Performance: Why caching improves performance

HIGH IMPACT

Caching reduces server response time and network load, improving page load speed and interaction responsiveness.

Serving repeated API responses efficiently

Express

const cache = new Map();
app.get('/data', async (req, res) => {
  if (cache.has('data')) {
    return res.json(cache.get('data'));
  }
  const data = await fetchFromDatabase();
  cache.set('data', data);
  res.json(data);
});

Returns cached data instantly on repeated requests, reducing database calls and response time.

📈 Performance GainReduces server response time to under 10 ms, lowers CPU usage significantly

Serving repeated API responses efficiently

Express

app.get('/data', async (req, res) => {
  const data = await fetchFromDatabase();
  res.json(data);
});

Fetches data from the database on every request, causing slow responses and high server load.

📉 Performance CostBlocks rendering for 100+ ms per request, increases server CPU usage

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No caching, fetch on every request	N/A	N/A	High due to slow data arrival	[X] Bad
In-memory caching for repeated data	N/A	N/A	Low, fast data delivery	[OK] Good

Rendering Pipeline

Caching reduces the time spent waiting for server data, allowing the browser to start rendering sooner and improving the overall user experience.

→Network

→Server Processing

→First Paint

⚠️ BottleneckServer Processing and Network Latency

Core Web Vital Affected

LCP

Caching reduces server response time and network load, improving page load speed and interaction responsiveness.

Optimization Tips

1Cache frequently requested data to reduce server load and speed up responses.

2Use in-memory or external caches to avoid repeated expensive operations.

3Monitor cache hit rates to ensure caching is effective and up to date.

Performance Quiz - 3 Questions

How does caching improve web performance in Express apps?

A By increasing the number of database queries

B By reducing server processing time and network latency for repeated requests

C By forcing the browser to reload all resources every time

D By adding extra data to each response

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and observe response times for repeated requests.

What to look for: Look for faster response times and smaller payloads on cached requests indicating improved performance.

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