Redis for distributed caching in Node.js - Mini Project: Build & Apply

Redis for distributed caching with Node.js

📖 Scenario: You are building a simple Node.js app that fetches user data from a slow database. To speed things up, you want to use Redis as a distributed cache. This means storing user data temporarily in Redis so future requests are faster.

🎯 Goal: Build a Node.js script that connects to Redis, sets a user data cache, checks if the cache exists, and retrieves it if available.

📋 What You'll Learn

Create a Redis client connection

Define a user data object

Set a cache key with the user data in Redis

Check if the cache key exists and retrieve the cached data

💡 Why This Matters

🌍 Real World

Distributed caching with Redis is used in web apps to speed up data access and reduce load on databases.

💼 Career

Many backend developer roles require knowledge of caching strategies and Redis usage for scalable applications.

1

Create Redis client connection

Write code to import the createClient function from the redis package and create a Redis client called client. Then connect the client using await client.connect() inside an async function called main.

Node.js

import { createClient } from 'redis';

async function main() {
  // Your code here
}

main();

Hint

Use createClient() to make a Redis client. Connect it with await client.connect() inside an async function.

2

Define user data object

Inside the main function, create a constant called userData that holds this exact object: { id: 'u123', name: 'Alice', age: 30 }.

Node.js

import { createClient } from 'redis';

async function main() {
  const client = createClient();
  await client.connect();

  // Define userData object here
  // Your code here
}

main();

Hint

Create a constant userData with the exact keys and values shown.

3

Set user data cache in Redis

Use await client.set() to store the userData object in Redis under the key 'user:u123'. Convert userData to a JSON string using JSON.stringify(userData) before storing.

Node.js

import { createClient } from 'redis';

async function main() {
  const client = createClient();
  await client.connect();

  const userData = { id: 'u123', name: 'Alice', age: 30 };

  // Set Redis cache for userData
  // Your code here
}

main();

Hint

Use client.set with the key 'user:u123' and the JSON string of userData.

4

Check and retrieve cached user data

Use await client.get('user:u123') to get the cached user data from Redis. Store it in a constant called cachedData. Then parse it back to an object using JSON.parse(cachedData) and store in parsedData. Finally, close the Redis client connection with await client.quit().

Node.js

import { createClient } from 'redis';

async function main() {
  const client = createClient();
  await client.connect();

  const userData = { id: 'u123', name: 'Alice', age: 30 };

  await client.set('user:u123', JSON.stringify(userData));

  // Retrieve and parse cached data, then quit client
  // Your code here
}

main();

Hint

Use client.get to get the cached string, parse it with JSON.parse, and close the client with client.quit().

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