Redis for distributed caching in Node.js - Performance & Optimization

Performance: Redis for distributed caching

HIGH IMPACT

This affects server response time and reduces backend load by caching data close to the application.

Caching frequently requested data to speed up responses

Node.js

const cachedData = await redisClient.get('key');
if (cachedData) {
  res.send(JSON.parse(cachedData));
} else {
  const data = await fetchFromDatabase();
  await redisClient.set('key', JSON.stringify(data), { EX: 60 });
  res.send(data);
}

Reads from fast Redis cache first, reducing database calls and speeding up response.

📈 Performance GainReduces backend response time by 50-90%, improving LCP

Caching frequently requested data to speed up responses

Node.js

const data = await fetchFromDatabase(); // fetch every time without cache
res.send(data);

Fetching from the database on every request causes slow responses and high server load.

📉 Performance CostBlocks rendering for 100-300ms per request depending on DB speed

Performance Comparison

Pattern	Backend Calls	Response Time	Cache Hit Rate	Verdict
No caching	Database call every request	High (100-300ms+)	0%	[X] Bad
Redis caching	Database call only on cache miss	Low (10-50ms)	High (depends on TTL)	[OK] Good

Rendering Pipeline

Redis caching reduces backend processing time before the server sends HTML or data to the browser, speeding up the critical rendering path.

→Server Processing

→Network Transfer

→First Contentful Paint

⚠️ BottleneckBackend data fetching and processing

Core Web Vital Affected

LCP

This affects server response time and reduces backend load by caching data close to the application.

Optimization Tips

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

2Set appropriate expiration (TTL) on Redis keys to keep cache fresh and efficient.

3Avoid caching large or highly dynamic data that changes every request.

Performance Quiz - 3 Questions

How does Redis caching improve web page load speed?

A By reducing backend data fetch time and serving cached data quickly

B By increasing the size of the HTML sent to the browser

C By delaying server responses to batch requests

D By storing data only on the client side

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and check response times for API calls or HTML requests.

What to look for: Look for reduced response times and fewer backend delays indicating cache hits

Practice

1. What is the main benefit of using Redis for distributed caching in a Node.js application?

easy

A. It slows down data retrieval to ensure consistency.

B. It automatically writes data to disk for permanent storage.

C. It replaces the need for any database in the application.

D. It stores data in memory for very fast access across multiple servers.

Solution

1. Step 1: Understand Redis caching purpose

   Redis stores data in memory, which is much faster than disk storage.

2. Step 2: Recognize distributed caching advantage

   Redis can be shared across servers, speeding up data access in distributed systems.

3. Final Answer:

   It stores data in memory for very fast access across multiple servers. -> Option D

4. Quick Check:

   Redis = Fast in-memory cache [OK]

Hint: Redis caches in memory for speed, not disk storage [OK]

Common Mistakes:

• Confusing Redis with a permanent database
• Thinking Redis slows down data access
• Assuming Redis replaces all databases

2. Which of the following is the correct way to create a Redis client using the official Node.js Redis library with async/await?

easy

A. const client = redis.createClient(); await client.connect();

B. const client = redis.connectClient();

C. const client = new Redis(); client.connect();

D. const client = redis.createClient; client.connect();

Solution

1. Step 1: Recall official Redis client creation

   The official Redis client uses createClient() method to create a client instance.

2. Step 2: Connect client asynchronously

   After creating, you must call await client.connect() to establish connection.

3. Final Answer:

   const client = redis.createClient(); await client.connect(); -> Option A

4. Quick Check:

   createClient + await connect = correct syntax [OK]

Hint: Use createClient() then await connect() to start Redis client [OK]

Common Mistakes:

• Using incorrect method names like connectClient()
• Forgetting to await client.connect()
• Calling createClient without parentheses

3. Given this Node.js code using Redis client, what will be logged to the console?

const redis = require('redis');
async function test() {
  const client = redis.createClient();
  await client.connect();
  await client.set('key', 'value');
  const result = await client.get('key');
  console.log(result);
  await client.disconnect();
}
test();

medium

A. undefined

B. null

C. value

D. Error: client.get is not a function

Solution

1. Step 1: Set key-value pair in Redis

   The code sets 'key' to 'value' using await client.set('key', 'value').

2. Step 2: Retrieve the value for 'key'

   Using await client.get('key') returns the stored string 'value'.

3. Final Answer:

   value -> Option C

4. Quick Check:

   Set then get returns stored string [OK]

Hint: Set key then get key returns stored value string [OK]

Common Mistakes:

• Expecting undefined or null instead of stored value
• Confusing async calls without await
• Assuming get returns an object instead of string

4. What is the error in this Node.js Redis code snippet?

const redis = require('redis');
const client = redis.createClient();
client.connect();
client.set('foo', 'bar');
const val = client.get('foo');
console.log(val);

medium

A. Redis client does not support set and get methods.

B. Missing await before async calls causing unresolved promises.

C. Calling createClient without parentheses.

D. Using require instead of import for Redis client.

Solution

1. Step 1: Identify async Redis methods

   client.connect(), client.set(), and client.get() return promises and must be awaited.

2. Step 2: Recognize missing await usage

   Without await, val is a promise, so console.log(val) logs a Promise object, not the value.

3. Final Answer:

   Missing await before async calls causing unresolved promises. -> Option B

4. Quick Check:

   Async Redis calls need await [OK]

Hint: Always await async Redis calls to get actual results [OK]

Common Mistakes:

• Not awaiting client.get causing Promise logged
• Assuming require is invalid in Node.js
• Thinking Redis client lacks set/get methods

5. You want to cache user profile data in Redis to reduce database calls. Which approach correctly handles cache misses and updates the cache in Node.js?

hard

A. Try to get data from Redis; if null, fetch from DB, then set Redis cache with the data.

B. Always fetch from DB and update Redis cache without checking Redis first.

C. Set Redis cache with empty string before fetching DB to avoid cache misses.

D. Fetch from Redis and DB simultaneously and use whichever returns first.

Solution

1. Step 1: Check Redis cache first

   Attempt to get user profile from Redis to avoid unnecessary DB calls.

2. Step 2: On cache miss, fetch from DB and update Redis

   If Redis returns null, fetch from database, then store result in Redis for future fast access.

3. Final Answer:

   Try to get data from Redis; if null, fetch from DB, then set Redis cache with the data. -> Option A

4. Quick Check:

   Cache miss handled by DB fetch then cache update [OK]

Hint: Check cache first; on miss, fetch DB then update cache [OK]

Common Mistakes:

• Skipping cache check and always querying DB
• Setting empty cache values causing wrong data
• Fetching DB and cache simultaneously causing race conditions