Redis for distributed caching in Node.js - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Redis in the context of distributed caching?

Redis is a fast, in-memory data store used to cache data across multiple servers, helping apps quickly access shared information without hitting the main database every time.

beginner

Why use distributed caching with Redis instead of local memory caching?

Distributed caching with Redis allows multiple servers to share the same cached data, ensuring consistency and reducing duplicate work, unlike local memory caching which is isolated per server.

beginner

How does Redis improve application performance in Node.js apps?

Redis stores frequently used data in memory, so Node.js apps can quickly retrieve it without slow database queries, reducing response times and server load.

beginner

What Node.js package is commonly used to connect to Redis?

The 'redis' npm package is commonly used to connect Node.js applications to Redis servers, providing easy commands to set, get, and manage cached data.

intermediate

What is a cache miss and how does Redis handle it?

A cache miss happens when requested data is not found in Redis. The app then fetches data from the main database, stores it in Redis for future requests, and returns it to the user.

What type of data store is Redis?

A File system

B Relational database

C In-memory key-value store

D Message queue

Redis stores data in memory as key-value pairs, making it very fast for caching.

Why is Redis suitable for distributed caching?

A Because it stores data on local disk only

B Because it uses slow disk access

C Because it is a relational database

D Because it allows multiple servers to share cached data

Redis allows multiple servers to access the same cached data, enabling distributed caching.

Which Node.js package is used to interact with Redis?

A redis

B mongoose

C express

D socket.io

The 'redis' package provides commands to connect and use Redis in Node.js.

What happens on a cache miss in Redis?

A Data is returned from Redis anyway

B The app fetches data from the main database and caches it

C Redis shuts down

D The app crashes

On a cache miss, the app gets data from the database, stores it in Redis, then returns it.

Which of these is NOT a benefit of using Redis for caching?

A Data persistence like a hard drive

B Faster data access

C Reduced database load

D Shared cache across servers

Redis is mainly an in-memory store; while it can persist data, its primary benefit is fast memory access, not hard drive persistence.

Explain how Redis helps improve performance in a Node.js app using distributed caching.

Think about how sharing data in memory helps many servers avoid slow database calls.

Describe what happens during a cache miss when using Redis for distributed caching.

Consider the steps from missing cache data to serving the user.

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