Redis ZRANGESTORE in Node.js (Detailed Guide w/ Code Examples)

Use Case(s)

The ZRANGE command in Redis fetches a range of members from a sorted set, where members are sorted by their scores. However, the ZRANGESTORE command is an extension that not only retrieves these ranges but also stores them into a new destination key, avoiding the need for another round trip to the server if you need to reuse the result.

This is particularly useful for:

  1. Temporary aggregations: Storing results temporarily to quickly access top/bottom records.
  2. Data processing pipelines: Part of a larger pipeline where intermediate results are stored and further processed or queried.
  3. Leaderboards or rankings: Easily managing sub-leaderboards or time-window-based leaderboards.

Code Examples

Example 1: Basic Usage of ZRANGESTORE

const redis = require('redis'); const client = redis.createClient(); // Connect to Redis server client.connect(); // Assuming "game-scores" is a sorted set with player scores // This command will store the top 3 players into a new key "top-scores" client.zRangeStore('top-scores', 'game-scores', 0, 2).then(result => { console.log(`Number of elements stored: ${result}`); }).catch(err => { console.error(`Error: ${err}`); }); client.quit();

In this example, we use zRangeStore to retrieve the top 3 scores from game-scores and store them in top-scores. The parameters 0 and 2 specify the start and stop indexes.

Example 2: Using WITHSCORES option

// Store the top 3 players along with their scores client.zRangeStore('top-scores-with-scores', 'game-scores', 0, 2, { WITHSCORES: true }).then(result => { console.log(`Number of elements stored: ${result}`); }).catch(err => { console.error(`Error: ${err}`); }); client.quit();

Here, the WITHSCORES option ensures that the scores are also stored alongside the members in the new key top-scores-with-scores.

Best Practices

  • Use appropriate key names: Ensure the destination key does not unintentionally overwrite important data.
  • Memory management: Be cautious with memory usage when duplicating large sets.

Common Mistakes

  • Ignoring asynchronous nature: Node.js Redis operations are asynchronous. Make sure to handle promises or use async/await to manage results properly.
  • Confusion with index bounds: Remember that Redis indices are inclusive.


Q: Can ZRANGESTORE be used with filters like specific score ranges? A: Yes, similar to ZRANGE, you can specify score ranges using options like BYSCORE.

Q: What happens if the destination key already exists? A: The existing key will be overwritten with the new range from the source key.

Was this content helpful?

Start building today

Dragonfly is fully compatible with the Redis ecosystem and requires no code changes to implement.