Set vs sorted set for membership in Redis - Visual Side-by-Side Comparison

Concept Flow - Set vs sorted set for membership

Start

↓

Check if element is in Set

|Yes↓

Return True

↓

End

No↓

Return False

↓

End

↓

Start

↓

Check if element is in Sorted Set

|Yes↓

Return True

↓

End

No↓

Return False

↓

End

Both Set and Sorted Set check if an element exists and return true or false. Sorted Set also maintains order but membership check works similarly.

Execution Sample

Redis

SADD myset apple banana cherry
SISMEMBER myset banana
ZADD myzset 1 apple 2 banana 3 cherry
ZSCORE myzset banana

Add elements to Set and Sorted Set, then check membership and score for 'banana'.

Execution Table

Step	Command	Action	Result	Explanation
1	SADD myset apple banana cherry	Add elements to Set	3	3 elements added to Set 'myset'
2	SISMEMBER myset banana	Check if 'banana' in Set	1	'banana' is a member, returns 1 (true)
3	ZADD myzset 1 apple 2 banana 3 cherry	Add elements with scores to Sorted Set	3	3 elements added to Sorted Set 'myzset'
4	ZSCORE myzset banana	Get score of 'banana' in Sorted Set	2	'banana' has score 2
5	ZSCORE myzset orange	Get score of 'orange' in Sorted Set	nil	'orange' not in Sorted Set, returns nil
6	ZSCORE myzset apple	Get score of 'apple' in Sorted Set	1	'apple' has score 1
7	ZSCORE myzset grape	Get score of 'grape' in Sorted Set	nil	'grape' not member, returns nil

💡 Commands complete; membership checks return 1 or nil indicating presence or absence.

Variable Tracker

Variable	Start	After Step 1	After Step 3	Final
myset	empty	{apple, banana, cherry}	{apple, banana, cherry}	{apple, banana, cherry}
myzset	empty	empty	{apple:1, banana:2, cherry:3}	{apple:1, banana:2, cherry:3}

Key Moments - 2 Insights

Why does SISMEMBER return 1 or 0 but ZSCORE returns a score or nil?

SISMEMBER returns 1 if element exists and 0 if not (boolean style). ZSCORE returns the element's score if it exists, or nil if it doesn't. So ZSCORE can be used to check membership by seeing if the result is nil or not (see execution_table rows 4-7).

Can we use Sorted Set membership check as fast as Set membership?

Yes, both Set and Sorted Set membership checks are fast (O(1) or O(log N)) in Redis. But Sorted Set stores scores which adds extra data, while Set only stores elements (see variable_tracker showing extra score data in myzset).

Visual Quiz - 3 Questions

Look at the execution_table, what does SISMEMBER myset banana return at step 2?

A 0

B 1

C nil

D banana

💡 Hint

Check the 'Result' column in execution_table row 2.

At which step does ZSCORE return nil indicating the element is not in the sorted set?

A Step 4

B Step 6

C Step 5

D Step 7

💡 Hint

Look for 'nil' in the 'Result' column in execution_table.

If we add 'orange' to myzset with score 4, what will ZSCORE myzset orange return?

A 1

B nil

C 4

D banana

💡 Hint

ZSCORE returns the score of the element if it exists, see step 4 for banana's score.

Concept Snapshot

Set stores unique elements with fast membership checks.
Sorted Set stores elements with scores, maintaining order.
SISMEMBER returns 1 if element exists, 0 if not.
ZSCORE returns element's score or nil if absent.
Use SISMEMBER for simple membership, ZSCORE for membership plus score info.

Full Transcript

This visual execution compares Redis Set and Sorted Set for membership checks. First, elements are added to a Set and a Sorted Set. Then, SISMEMBER checks if 'banana' is in the Set, returning 1 for true. ZSCORE retrieves the score of 'banana' in the Sorted Set, returning 2. If an element is not present, ZSCORE returns nil. Both data structures allow fast membership checks, but Sorted Set also stores scores for ordering. SISMEMBER returns 1 or 0, while ZSCORE returns a score or nil. This helps decide which to use based on whether you need ordering or just membership.