Redis integration for distributed cache in Express - Mini Project: Build & Apply

Redis integration for distributed cache

📖 Scenario: You are building a simple Express server that uses Redis as a distributed cache to store and retrieve user session data quickly.

🎯 Goal: Create an Express app that connects to Redis, sets a cache entry for a user session, and retrieves it on request.

📋 What You'll Learn

Create a Redis client using the redis package

Configure the Redis client connection

Set a user session key-value pair in Redis

Retrieve the user session data from Redis in an Express route

💡 Why This Matters

🌍 Real World

Redis is widely used to cache session data, speeding up web applications by reducing database load.

💼 Career

Understanding Redis integration is valuable for backend developers working on scalable, high-performance web services.

1

Setup Redis client

Create a Redis client using createClient() from the redis package and assign it to a constant called redisClient.

Express

// Your code here

Hint

Use import { createClient } from 'redis' and then const redisClient = createClient().

2

Connect Redis client

Add an async function called connectRedis that calls await redisClient.connect() to connect the Redis client.

Express

import express from 'express';
import { createClient } from 'redis';

const redisClient = createClient();

// Your code here

Hint

Define async function connectRedis() and inside it call await redisClient.connect().

3

Set user session in Redis

Inside an Express route /set-session, use await redisClient.set() to store the key user:123 with value "active".

Express

import express from 'express';
import { createClient } from 'redis';

const redisClient = createClient();

async function connectRedis() {
    await redisClient.connect();
}

await connectRedis();

const app = express();

// Your code here

Hint

Create a GET route /set-session and inside use await redisClient.set('user:123', 'active').

4

Retrieve user session from Redis

Add an Express route /get-session that uses await redisClient.get('user:123') to get the session value and sends it in the response.

Express

import express from 'express';
import { createClient } from 'redis';

const redisClient = createClient();

async function connectRedis() {
    await redisClient.connect();
}

await connectRedis();

const app = express();

app.get('/set-session', async (req, res) => {
    await redisClient.set('user:123', 'active');
    res.send('Session set');
});

// Your code here

Hint

Create a GET route /get-session and inside use await redisClient.get('user:123') to retrieve the session.

Practice

1. What is the main benefit of integrating Redis as a distributed cache in an Express application?

easy

A. It speeds up data access by storing shared data in memory across servers.

B. It replaces the need for a database entirely.

C. It automatically scales the Express server instances.

D. It provides a user interface for managing Express routes.

Solution

1. Step 1: Understand Redis role in caching

   Redis stores data in memory, making data access very fast compared to disk-based storage.

2. Step 2: Recognize distributed cache benefit

   Redis can be shared across multiple servers, so all Express instances access the same cached data, improving speed and consistency.

3. Final Answer:

   It speeds up data access by storing shared data in memory across servers. -> Option A

4. Quick Check:

   Redis cache = fast shared data [OK]

Hint: Redis caches shared data in memory for speed [OK]

Common Mistakes:

• Thinking Redis replaces the database
• Confusing Redis with server scaling tool
• Assuming Redis manages Express routes

2. Which of the following is the correct way to create a Redis client in an Express app using the latest redis package?

easy

A. const client = new Redis(); client.start();

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

C. const client = redis.connectClient();

D. const client = redis.create(); client.open();

Solution

1. Step 1: Recall redis package usage

   The modern redis package uses createClient() to create a client instance.

2. Step 2: Connect the client

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

3. Final Answer:

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

4. Quick Check:

   createClient + connect = correct syntax [OK]

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

Common Mistakes:

• Using non-existent methods like start() or open()
• Calling connectClient() which does not exist
• Instantiating Redis with new Redis() incorrectly

3. Given this Express route using Redis cache:

app.get('/data', async (req, res) => {
  const cacheKey = 'myData';
  const cached = await client.get(cacheKey);
  if (cached) return res.send(JSON.parse(cached));
  const data = { value: 42 };
  await client.set(cacheKey, JSON.stringify(data), { EX: 10 });
  res.send(data);
});

What happens when you call /data twice within 10 seconds?

medium

A. The first call stores data in cache, second call returns cached data.

B. The first call fetches from cache, second call fetches fresh data.

C. Both calls fetch fresh data and store it in cache.

D. Both calls return cached data without storing anything.

Solution

1. Step 1: Analyze first call behavior

   On first call, cache is empty, so data is created and stored with 10 seconds expiration.

2. Step 2: Analyze second call within 10 seconds

   Second call finds cached data and returns it directly without recreating or resetting cache.

3. Final Answer:

   The first call stores data in cache, second call returns cached data. -> Option A

4. Quick Check:

   Cache empty first, then hit cache [OK]

Hint: First call caches, second call uses cache within expiry [OK]

Common Mistakes:

• Assuming cache is refreshed on every call
• Thinking cache is never used
• Ignoring expiration time effect

4. Consider this Express code snippet using Redis:

app.get('/count', async (req, res) => {
  const count = await client.get('count');
  const newCount = count + 1;
  await client.set('count', newCount);
  res.send({ count: newCount });
});

What issue will occur when this route is called?

medium

A. SyntaxError due to incorrect async function syntax.

B. ReferenceError because client is not defined.

C. count is a string from Redis, so count + 1 performs string concatenation instead of numeric addition.

D. No error; the count increments correctly.

Solution

1. Step 1: Identify data type of count

   Redis stores values as strings, so count is a string when retrieved (null on first call).

2. Step 2: Analyze addition operation

   Adding number 1 to a string (after first call) results in string concatenation (e.g., "1" + 1 = "11").

3. Step 3: Predict issue

   This causes incorrect count values like 1, "11", "111", etc., instead of proper increments 1, 2, 3.

4. Final Answer:

   count is a string from Redis, so count + 1 performs string concatenation instead of numeric addition. -> Option C

5. Quick Check:

   String + number without conversion = concatenation [OK]

Hint: Convert Redis string to number before adding [OK]

Common Mistakes:

• Assuming Redis returns numbers directly
• Ignoring async/await correctness
• Thinking no error occurs

5. You want to cache user profile data in Redis with a 5-minute expiration in an Express app. Which code snippet correctly sets the cache with expiration and handles errors properly?

hard

A. client.set('user:123', JSON.stringify(profile)); setTimeout(() => client.del('user:123'), 300000);

B. client.set('user:123', JSON.stringify(profile), 300);
console.log('Cache set');

C. await client.set('user:123', profile, { expire: 300 });

D. try {
await client.set('user:123', JSON.stringify(profile), { EX: 300 });
} catch (err) {
console.error('Cache error:', err);
}

Solution

1. Step 1: Use correct Redis set syntax with expiration

   The redis client set method accepts options with EX for expiration in seconds, so { EX: 300 } is correct.

2. Step 2: Handle errors with try-catch

   Since set is async, wrapping in try-catch ensures errors are caught and logged properly.

3. Step 3: Check other options for mistakes

   client.set('user:123', JSON.stringify(profile), 300); console.log('Cache set'); misses async/await and uses wrong expiration argument; C uses wrong option key; D manually deletes cache but is less efficient.

4. Final Answer:

   try { await client.set('user:123', JSON.stringify(profile), { EX: 300 }); } catch (err) { console.error('Cache error:', err); } -> Option D

5. Quick Check:

   set with EX + try-catch = correct [OK]

Hint: Use { EX: seconds } option and try-catch for errors [OK]

Common Mistakes:

• Passing expiration as a separate argument
• Not stringifying objects before caching
• Ignoring async error handling