Redis with Node.js (ioredis) - Time & Space Complexity

Time Complexity: Redis with Node.js (ioredis)

O(n)

Understanding Time Complexity

When using Redis with Node.js through ioredis, it's important to understand how the time to run commands grows as data size increases.

We want to know how the number of operations changes when we run commands like fetching or setting many keys.

Scenario Under Consideration

Analyze the time complexity of the following Redis commands using ioredis.

const Redis = require('ioredis');
const redis = new Redis();

async function getMultipleKeys(keys) {
  const pipeline = redis.pipeline();
  keys.forEach(key => pipeline.get(key));
  const results = await pipeline.exec();
  return results.map(result => result[1]);
}
    

This code fetches multiple keys from Redis using a pipeline to send all requests at once.

Identify Repeating Operations

Look for repeated actions that affect time.

• Primary operation: Sending a GET command for each key in the list.
• How many times: Once for each key in the input array.

How Execution Grows With Input

As the number of keys grows, the number of GET commands grows the same way.

Input Size (n)	Approx. Operations
10	10 GET commands sent
100	100 GET commands sent
1000	1000 GET commands sent

Pattern observation: The number of operations grows directly with the number of keys.

Final Time Complexity

Time Complexity: O(n)

This means the time to get all keys grows in a straight line as you add more keys.

Common Mistake

[X] Wrong: "Using pipeline makes the time constant no matter how many keys we get."

[OK] Correct: Pipeline reduces network delays but still sends one command per key, so time grows with the number of keys.

Interview Connect

Understanding how Redis commands scale helps you explain your choices clearly and shows you know how to handle data efficiently in real projects.

Self-Check

"What if we replaced pipeline with individual get calls without batching? How would the time complexity change?"

Practice

1. What does the set method do in ioredis when used with Node.js?

easy

A. Stores a value with a specified key in Redis

B. Retrieves a value from Redis by key

C. Deletes a key-value pair from Redis

D. Connects to the Redis server

Solution

1. Step 1: Understand the purpose of set in Redis

   The set method is used to store data by assigning a value to a key in Redis.

2. Step 2: Differentiate from other methods

   get retrieves data, del deletes data, and connection is handled separately.

3. Final Answer:

   Stores a value with a specified key in Redis -> Option A

4. Quick Check:

   set stores data [OK]

Hint: Remember: set = save data, get = read data [OK]

Common Mistakes:

• Confusing set with get
• Thinking set deletes data
• Assuming set connects to Redis

2. Which of the following is the correct syntax to get a value for key 'name' using ioredis with async/await?

easy

A. const value = redis.get('name');

B. const value = redis.getSync('name');

C. const value = await redis.set('name');

D. const value = await redis.get('name');

Solution

1. Step 1: Recognize async nature of ioredis commands

   ioredis commands return promises, so await is needed to get the resolved value.

2. Step 2: Identify correct method and usage

   get retrieves the value; set stores data; getSync does not exist.

3. Final Answer:

   const value = await redis.get('name'); -> Option D

4. Quick Check:

   Use await with get [OK]

Hint: Always use await with async Redis calls [OK]

Common Mistakes:

• Omitting await causing unresolved promises
• Using non-existent getSync method
• Using set instead of get to read data

3. What will be the output of the following code snippet?

const Redis = require('ioredis');
const redis = new Redis();

async function test() {
  await redis.set('color', 'blue');
  const val = await redis.get('color');
  console.log(val);
}
test();

medium

A. null

B. undefined

C. blue

D. SyntaxError

Solution

1. Step 1: Analyze the set command

   The code stores the string 'blue' with key 'color' in Redis asynchronously.

2. Step 2: Analyze the get command and console output

   The code retrieves the value for 'color' and logs it, which should be 'blue'.

3. Final Answer:

   blue -> Option C

4. Quick Check:

   set then get returns stored value [OK]

Hint: set then get returns stored value [OK]

Common Mistakes:

• Forgetting await causing undefined output
• Assuming get returns null if key exists
• Syntax errors from missing async

4. Identify the error in the following code snippet using ioredis:

const Redis = require('ioredis');
const redis = new Redis();

function getValue() {
  const value = redis.get('key');
  console.log(value);
}
getValue();

medium

A. Missing await causing value to be a Promise

B. Incorrect Redis import statement

C. Redis client not connected

D. Using console.log inside function is invalid

Solution

1. Step 1: Understand async nature of redis.get

   The get method returns a Promise, so without await, value is a Promise object.

2. Step 2: Identify missing await and its effect

   Logging value prints a Promise, not the actual stored value.

3. Final Answer:

   Missing await causing value to be a Promise -> Option A

4. Quick Check:

   Always await async Redis calls [OK]

Hint: Always await redis.get to get actual value [OK]

Common Mistakes:

• Ignoring async/await causing Promise logs
• Thinking Redis import is wrong
• Assuming console.log inside function is invalid

5. You want to store a user's session data as a JSON object in Redis using ioredis. Which approach correctly stores and retrieves the session data?

hard

A. Store session as multiple keys like set('session:user', user) and set('session:data', data)

B. Use set('session', JSON.stringify(session)) to store and JSON.parse(await get('session')) to retrieve

C. Use hmset('session', session) without stringifying and hgetall('session') to retrieve

D. Use set('session', session) directly and await get('session') to retrieve

Solution

1. Step 1: Understand Redis stores strings

   Redis stores strings, so objects must be converted to strings before storing.

2. Step 2: Use JSON methods to store and retrieve objects

   Use JSON.stringify to convert object to string before storing, and JSON.parse to convert back after retrieving.

3. Final Answer:

   Use set('session', JSON.stringify(session)) to store and JSON.parse(await get('session')) to retrieve -> Option B

4. Quick Check:

   Stringify before set, parse after get [OK]

Hint: Stringify objects before set, parse after get [OK]

Common Mistakes:

• Trying to store objects directly without stringifying
• Using hash commands without proper structure
• Splitting session into multiple keys unnecessarily