Redis for distributed caching in Node.js - Step-by-Step Execution

Concept Flow - Redis for distributed caching

App requests data

↓

Check Redis cache

↓

Return cached

↓

Send response

The app first checks Redis cache for data. If found, it returns cached data. If not, it fetches from database, stores it in Redis, then returns it.

Execution Sample

Node.js

const redis = require('redis');
const client = redis.createClient();

client.connect();

async function getData(key) {
  const cache = await client.get(key);
  let data;
  if (cache) {
    data = JSON.parse(cache);
  } else {
    data = await fetchFromDB(key);
    await client.set(key, JSON.stringify(data));
  }
  return data;
}

This code tries to get data from Redis cache first; if missing, it fetches from DB, caches it, then returns.

Execution Table

Step	Action	Redis GET Result	DB Fetch	Redis SET	Return Value
1	Call getData('user:1')	null	No	No	No
2	Redis GET 'user:1'	null	No	No	No
3	Cache miss, fetch from DB	null	User data from DB	No	No
4	Store data in Redis	null	User data from DB	Set user:1	No
5	Return fetched data	null	User data from DB	Set user:1	User data from DB
6	Call getData('user:1') again	User data JSON	No	No	No
7	Redis GET 'user:1'	User data JSON	No	No	No
8	Cache hit, parse and return	User data JSON	No	No	User data from cache

💡 Execution stops after returning data from cache or DB.

Variable Tracker

Variable	Start	After Step 3	After Step 5	After Step 8
cache	undefined	null	null	User data JSON string
data	undefined	User data from DB	User data from DB	User data from cache (parsed)

Key Moments - 3 Insights

Why do we check Redis before fetching from the database?

Because Redis is a fast cache; checking it first avoids slow database calls if data is already cached, as shown in execution_table steps 2 and 7.

What happens if Redis returns null?

It means cache miss; then the code fetches data from the database and stores it in Redis, as seen in steps 3 and 4.

Why do we store data in Redis after fetching from DB?

To speed up future requests by caching the data, so next time Redis GET returns the data directly, shown in step 4 storing and step 8 returning.

Visual Quiz - 3 Questions

Look at the execution_table, what is the Redis GET result at step 7?

A Error

B null

C User data JSON

D Undefined

💡 Hint

Check the 'Redis GET Result' column at step 7 in the execution_table.

At which step does the code fetch data from the database?

A Step 2

B Step 3

C Step 6

D Step 8

💡 Hint

Look for the 'DB Fetch' column showing 'User data from DB' in the execution_table.

If Redis always returns data, which steps would be skipped?

A Steps 3 and 4

B Steps 1 and 2

C Steps 5 and 6

D Steps 7 and 8

💡 Hint

Refer to execution_table steps where DB fetch and Redis set happen.

Concept Snapshot

Redis caching flow:
1. App requests data.
2. Check Redis cache with GET.
3. If cache miss, fetch from DB.
4. Store DB data in Redis with SET.
5. Return data to app.
This speeds up repeated data access.

Full Transcript

This visual execution shows how Redis is used for distributed caching in a Node.js app. When the app requests data, it first checks Redis cache using GET. If Redis returns null, it means the data is not cached, so the app fetches it from the database. Then, it stores the fetched data in Redis using SET for future fast access. If Redis returns data, the app parses and returns it immediately, avoiding a database call. This process improves performance by reducing database load and speeding up data retrieval.

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