Redis as cache vs data store vs message broker - Visual Side-by-Side Comparison

Concept Flow - Redis as cache vs data store vs message broker

Client Request

↓

Cache

↓

Fast Read

↓

Return Data

Client sends request; Redis handles it differently based on use: cache for fast reads, data store for persistence, or message broker for communication.

Execution Sample

Redis

SET user:1 "Alice"
GET user:1
PUBLISH channel1 "Hello"
SUBSCRIBE channel1

Shows Redis commands used as cache (SET/GET), data store (SET/GET), and message broker (PUBLISH/SUBSCRIBE).

Execution Table

Step	Command	Action	Redis Role	Result
1	SET user:1 "Alice"	Store key-value	Cache/Data Store	OK
2	GET user:1	Retrieve value	Cache/Data Store	"Alice"
3	PUBLISH channel1 "Hello"	Send message	Message Broker	Number of subscribers notified
4	SUBSCRIBE channel1	Listen to messages	Message Broker	Subscribed to channel1
5	GET user:2	Retrieve missing key	Cache/Data Store	nil
6	END	No more commands	-	-

💡 Execution stops after all commands processed.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
user:1	nil	"Alice"	"Alice"	"Alice"	"Alice"	"Alice"
channel1_subscribed	false	false	false	false	true	true

Key Moments - 2 Insights

Why does GET user:2 return nil in step 5?

Because user:2 was never set, Redis returns nil indicating no data found, as shown in execution_table row 5.

How does Redis handle PUBLISH and SUBSCRIBE differently from SET and GET?

PUBLISH sends messages to subscribers without storing data, while SET/GET store and retrieve data. This difference is clear in execution_table rows 1-4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result of the GET command at step 2?

A "Alice"

B nil

C OK

D Error

💡 Hint

Check the 'Result' column at step 2 in execution_table.

At which step does Redis subscribe to a channel?

A Step 3

B Step 2

C Step 4

D Step 1

💡 Hint

Look at the 'Command' and 'Action' columns in execution_table for subscription.

If we remove the SET command at step 1, what would GET user:1 return at step 2?

A "Alice"

B nil

C OK

D Error

💡 Hint

Refer to variable_tracker for user:1 value before and after step 1.

Concept Snapshot

Redis can be used in three main ways:
- Cache: temporary fast storage using SET/GET
- Data Store: persistent key-value storage
- Message Broker: send/receive messages with PUBLISH/SUBSCRIBE
Each use changes how Redis handles commands and data flow.

Full Transcript

This visual execution shows how Redis works differently as a cache, data store, and message broker. Commands like SET and GET store and retrieve data for cache or data store roles. PUBLISH and SUBSCRIBE handle messaging without storing data. The execution table traces each command step-by-step, showing results and state changes. Variable tracking shows key values and subscription status. Key moments clarify why missing keys return nil and how messaging differs from data storage. The quiz tests understanding of command results and Redis roles.

Practice

1. Which of the following best describes Redis when used as a cache?

easy

A. It sends messages between different parts of an app.

B. It permanently stores large amounts of data for apps.

C. It temporarily stores data to speed up app responses.

D. It analyzes data to find patterns automatically.

Solution

1. Step 1: Understand Redis cache role

   Redis cache stores data temporarily to help apps respond faster by avoiding repeated data fetching.

2. Step 2: Compare other roles

   Permanent storage is data store, messaging is message broker, and analysis is not Redis's main role.

3. Final Answer:

   It temporarily stores data to speed up app responses. -> Option C

4. Quick Check:

   Cache = Temporary fast storage [OK]

Hint: Cache means temporary fast storage to speed apps [OK]

Common Mistakes:

• Confusing cache with permanent data store
• Thinking Redis analyzes data automatically
• Mixing message broker role with cache

2. Which Redis command is used to publish a message to a channel when Redis acts as a message broker?

easy

A. SET

B. PUBLISH

C. GET

D. SUBSCRIBE

Solution

1. Step 1: Identify publish command in Redis

   The PUBLISH command sends a message to subscribers on a channel in Redis's message broker role.

2. Step 2: Differentiate from other commands

   SET stores data, GET retrieves data, SUBSCRIBE listens to messages but does not send them.

3. Final Answer:

   PUBLISH -> Option B

4. Quick Check:

   Send message = PUBLISH [OK]

Hint: Publish sends messages; subscribe listens [OK]

Common Mistakes:

• Using SET or GET to send messages
• Confusing SUBSCRIBE with PUBLISH
• Thinking GET publishes messages

3. Consider this Redis usage: You store user session data with expiration times to speed up login checks. What role is Redis playing here?

medium

A. Cache

B. Message broker

C. Data store

D. Analytics engine

Solution

1. Step 1: Analyze session data with expiration

   Storing data with expiration to speed up access fits caching, as data is temporary and speeds up app.

2. Step 2: Exclude other roles

   Message broker sends messages, data store keeps permanent data, analytics engine is unrelated.

3. Final Answer:

   Cache -> Option A

4. Quick Check:

   Temporary session data = Cache [OK]

Hint: Temporary data with expiry means cache [OK]

Common Mistakes:

• Thinking session data is permanent storage
• Confusing message broker with cache
• Assuming analytics role for session data

4. You wrote this Redis command to send a message: SUBSCRIBE news. What is wrong if your goal was to send a message?

medium

A. SUBSCRIBE deletes the channel.

B. SUBSCRIBE command syntax is incorrect.

C. SUBSCRIBE stores messages permanently.

D. SUBSCRIBE is for receiving messages, not sending.

Solution

1. Step 1: Understand SUBSCRIBE command purpose

   SUBSCRIBE listens to messages on a channel; it does not send messages.

2. Step 2: Identify correct sending command

   To send messages, use PUBLISH, not SUBSCRIBE.

3. Final Answer:

   SUBSCRIBE is for receiving messages, not sending. -> Option D

4. Quick Check:

   SUBSCRIBE = receive, PUBLISH = send [OK]

Hint: Subscribe listens; publish sends messages [OK]

Common Mistakes:

• Using SUBSCRIBE to send messages
• Thinking SUBSCRIBE deletes channels
• Believing SUBSCRIBE stores messages

5. You want to use Redis to both speed up data access and send notifications between app parts. Which setup correctly uses Redis roles?

hard

A. Use Redis as a cache for data and use PUBLISH/SUBSCRIBE for messaging.

B. Use Redis only as a data store and ignore messaging features.

C. Use Redis as a message broker only, not for caching.

D. Use Redis to permanently store messages and cache data simultaneously.

Solution

1. Step 1: Identify Redis roles for caching and messaging

   Redis can cache data to speed access and use PUBLISH/SUBSCRIBE commands to send messages between app parts.

2. Step 2: Exclude incorrect setups

   Ignoring messaging misses notification need; message broker only misses caching; permanent message storage is not typical.

3. Final Answer:

   Use Redis as a cache for data and use PUBLISH/SUBSCRIBE for messaging. -> Option A

4. Quick Check:

   Cache + Pub/Sub = correct multi-role use [OK]

Hint: Combine cache and pub/sub for speed and messaging [OK]

Common Mistakes:

• Using Redis only for one role when multiple needed
• Trying to store messages permanently in Redis
• Ignoring pub/sub for notifications