List vs sorted set for sequences in Redis

Introduction

Lists and sorted sets are two ways to store sequences in Redis. They help keep items in order but work differently.

When you want to keep items in the order they were added and access them by position.

When you need to store items with a score to sort them automatically.

When you want to add or remove items quickly from the start or end of a sequence.

When you want to get items sorted by a custom score, like timestamps or priorities.

When you want to avoid duplicates and keep items unique with a score.

Syntax

Redis

List commands:
LPUSH key value1 [value2 ...]  # Add items to the start
RPUSH key value1 [value2 ...]  # Add items to the end
LRANGE key start stop          # Get items by index range

Sorted Set commands:
ZADD key score1 member1 [score2 member2 ...]  # Add items with scores
ZRANGE key start stop [WITHSCORES]            # Get items by rank range
ZRANGEBYSCORE key min max [WITHSCORES]         # Get items by score range

Lists keep order by insertion and allow duplicates.

Sorted sets keep items unique and order by score.

Examples

Adds "banana" and "apple" to the start of the list, then gets all items.

Redis

LPUSH mylist "apple" "banana"
LRANGE mylist 0 -1

Adds "apple" and "banana" to the end of the list, then gets all items.

Redis

RPUSH mylist "apple" "banana"
LRANGE mylist 0 -1

Adds "apple" with score 10 and "banana" with score 20, then gets all items with scores sorted by score.

Redis

ZADD myset 10 "apple" 20 "banana"
ZRANGE myset 0 -1 WITHSCORES

Adds "apple" and "banana" with scores, then gets items with scores between 0 and 10.

Redis

ZADD myset 10 "apple"
ZADD myset 5 "banana"
ZRANGEBYSCORE myset 0 10 WITHSCORES

Sample Program

This example shows how to add items to a list and a sorted set, then retrieve them. The list keeps insertion order. The sorted set orders by score.

Redis

# Using Redis CLI commands

# Create a list and add items
RPUSH fruits "apple"
RPUSH fruits "banana"
RPUSH fruits "cherry"

# Show list items
LRANGE fruits 0 -1

# Create a sorted set and add items with scores
ZADD fruit_scores 3 "apple"
ZADD fruit_scores 1 "banana"
ZADD fruit_scores 2 "cherry"

# Show sorted set items with scores
ZRANGE fruit_scores 0 -1 WITHSCORES

Important Notes

Lists are simple and fast for adding/removing items at ends (O(1) time).

Sorted sets keep items unique and sorted by score, but adding is O(log n) time.

Use lists when order of insertion matters and duplicates are allowed.

Use sorted sets when you need automatic sorting by score and uniqueness.

Summary

Lists store ordered sequences with duplicates allowed.

Sorted sets store unique items sorted by a numeric score.

Choose lists for simple order, sorted sets for scored sorting.

Practice

1. Which Redis data structure allows storing duplicate elements while preserving their order?

easy

A. Hash

B. List

C. Sorted Set

D. Set

Solution

1. Step 1: Understand List behavior

   Lists in Redis keep elements in the order they were added and allow duplicates.

2. Step 2: Compare with Sorted Set

   Sorted sets store unique elements sorted by score, so duplicates are not allowed.

3. Final Answer:

   List -> Option B

4. Quick Check:

   Duplicates allowed and order preserved = List [OK]

Hint: Duplicates allowed? Use List, not Sorted Set. [OK]

Common Mistakes:

• Thinking Sorted Set allows duplicates
• Confusing Sets with Lists
• Assuming Hashes store sequences

2. Which of the following Redis commands correctly adds an element with a score to a sorted set?

easy

A. HSET myhash field element

B. LPUSH mylist element

C. SADD myset element

D. ZADD myzset 10 element

Solution

1. Step 1: Identify command for sorted set insertion

   ZADD adds elements with a score to a sorted set.

2. Step 2: Check other commands

   LPUSH adds to list, SADD adds to set, HSET adds to hash field.

3. Final Answer:

   ZADD myzset 10 element -> Option D

4. Quick Check:

   ZADD = add with score [OK]

Hint: ZADD is for sorted sets with scores. [OK]

Common Mistakes:

• Using LPUSH for sorted sets
• Confusing SADD with ZADD
• Using HSET for sequences

3. Given the following Redis commands executed in order:
LPUSH mylist a
LPUSH mylist b
LPUSH mylist c
What will LRANGE mylist 0 -1 return?

medium

A. ["a", "b", "c"]

B. ["b", "c", "a"]

C. ["c", "b", "a"]

D. Error

Solution

1. Step 1: Understand LPUSH order

   LPUSH adds elements to the head (start) of the list, so last pushed is first.

2. Step 2: Trace the list after pushes

   LPUSH mylist a: ["a"], then LPUSH mylist b: ["b", "a"], then LPUSH mylist c: ["c", "b", "a"]. LRANGE mylist 0 -1 returns ["c", "b", "a"].

3. Final Answer:

   ["c", "b", "a"] -> Option C

4. Quick Check:

   LPUSH adds to head, so newest first [OK]

Hint: LPUSH adds to front; last pushed appears first. [OK]

Common Mistakes:

• Assuming LPUSH adds to tail
• Mixing order of elements
• Expecting error from LRANGE

4. You tried to add duplicate elements with different scores to a sorted set using:
ZADD myzset 1 element
ZADD myzset NX 2 element
But the score did not update as expected. What is the likely issue?

medium

A. Sorted sets do not allow duplicate elements; score updates require special flag

B. ZADD command syntax is incorrect

C. You must remove the element before adding it again

D. Redis lists should be used instead

Solution

1. Step 1: Understand sorted set uniqueness

   Sorted sets store unique elements; adding the same element updates its score by default.

2. Step 2: Check if score updates require flags

   By default, ZADD updates score if element exists; if it did not update, likely a misunderstanding or missing flag like NX or XX.

3. Final Answer:

   Sorted sets do not allow duplicate elements; score updates require special flag -> Option A

4. Quick Check:

   Sorted sets unique, score updates need care [OK]

Hint: Sorted sets unique; score updates may need flags. [OK]

Common Mistakes:

• Thinking duplicates allowed in sorted sets
• Assuming ZADD syntax is wrong
• Trying to remove before adding

5. You want to store a sequence of user actions with timestamps and retrieve them sorted by time, allowing multiple actions at the same timestamp. Which Redis data structure and approach is best?

hard

A. Use a Sorted Set with timestamps as scores; append a unique suffix to actions to allow duplicates

B. Use a List and store actions with timestamps as strings; order is insertion order

C. Use a Hash with timestamps as fields and actions as values

D. Use a Set to store actions; order does not matter

Solution

1. Step 1: Analyze requirement for sorting by timestamp

   Sorted sets sort elements by numeric score, perfect for timestamps.

2. Step 2: Handle duplicates with same timestamp

   Sorted sets require unique elements, so append unique suffix to actions to allow duplicates with same score.

3. Step 3: Compare with other options

   Lists preserve order but cannot sort by timestamp easily; hashes and sets do not maintain order or allow sorting by score.

4. Final Answer:

   Use a Sorted Set with timestamps as scores; append a unique suffix to actions to allow duplicates -> Option A

5. Quick Check:

   Sorted set + unique elements for timestamp sorting [OK]

Hint: Sorted set + unique suffix for duplicates with same score. [OK]

Common Mistakes:

• Using List but losing timestamp sorting
• Ignoring uniqueness in sorted sets
• Using Hash or Set which don't sort