SUBSCRIBE to channels in Redis - Step-by-Step Execution

Concept Flow - SUBSCRIBE to channels

Client sends SUBSCRIBE command

↓

Server registers client to channel(s)

↓

Server waits for messages on channel(s)

↓

Message published to channel

↓

Server sends message to subscribed client

↓

Client receives message

↓

Repeat for new messages or client unsubscribes

The client sends a SUBSCRIBE command to the server, which registers the client to listen to specified channels. When messages are published to those channels, the server forwards them to the client.

Execution Sample

Redis

SUBSCRIBE news sports

(Publisher) PUBLISH news "Hello News"

(Publisher) PUBLISH sports "Game Tonight"

Client subscribes to 'news' and 'sports' channels; messages published to these channels are received by the client.

Execution Table

Step	Action	Server State	Client Output
1	Client sends SUBSCRIBE news sports	Client registered to channels: news, sports	Subscription confirmation for news and sports
2	Publisher sends PUBLISH news "Hello News"	Message queued for clients subscribed to news	Received message on channel 'news': "Hello News"
3	Publisher sends PUBLISH sports "Game Tonight"	Message queued for clients subscribed to sports	Received message on channel 'sports': "Game Tonight"
4	No more messages	Waiting for new messages or unsubscribe	No output, waiting

💡 Execution waits indefinitely until client unsubscribes or connection closes

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
Subscribed Channels	[]	[news, sports]	[news, sports]	[news, sports]	[news, sports]
Received Messages	[]	[]	["Hello News"]	["Hello News", "Game Tonight"]	["Hello News", "Game Tonight"]

Key Moments - 3 Insights

Why does the client receive a confirmation message after subscribing?

After the SUBSCRIBE command (Step 1), the server sends a confirmation to the client listing the channels subscribed, confirming registration as shown in the Client Output column.

Does the client receive messages from channels it did not subscribe to?

No, only messages published to channels the client subscribed to are forwarded. For example, messages on 'news' and 'sports' are received, but not others.

Why does the server keep waiting after delivering messages?

The SUBSCRIBE mode keeps the connection open to continuously receive messages until the client unsubscribes or disconnects, as shown in Step 4.

Visual Quiz - 3 Questions

Look at the execution table, what channels is the client subscribed to after Step 1?

A [news, sports]

B [news]

C [sports]

D []

💡 Hint

Check the Server State and Client Output columns in Step 1

At which step does the client receive the message "Game Tonight"?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the Client Output column for the message content

If the client unsubscribes after Step 3, what happens at Step 4?

A Server sends more messages

B Client receives no more messages

C Client automatically resubscribes

D Server closes connection immediately

💡 Hint

Refer to the exit_note and Step 4 description

Concept Snapshot

SUBSCRIBE command registers client to channels
Server forwards published messages on those channels
Client receives messages asynchronously
Connection stays open until unsubscribe or disconnect
Used for real-time message delivery

Full Transcript

The SUBSCRIBE command in Redis lets a client listen to one or more channels. When the client sends SUBSCRIBE with channel names, the server registers the client to those channels and confirms the subscription. Whenever a message is published to any of those channels, the server sends the message to the client. The client keeps receiving messages until it unsubscribes or disconnects. This allows real-time message delivery through channels.

Practice

1. What does the Redis SUBSCRIBE command do?

easy

A. Connects the client to one or more channels to receive messages

B. Deletes a channel and all its messages

C. Saves the current database state to disk

D. Lists all keys matching a pattern

Solution

1. Step 1: Understand the purpose of SUBSCRIBE

   The SUBSCRIBE command is used to listen to messages published on channels in Redis.

2. Step 2: Identify the correct function

   Only Connects the client to one or more channels to receive messages describes connecting to channels to receive live messages, which matches SUBSCRIBE's purpose.

3. Final Answer:

   Connects the client to one or more channels to receive messages -> Option A

4. Quick Check:

   SUBSCRIBE = Connect to channels [OK]

Hint: SUBSCRIBE means listen to channels for messages [OK]

Common Mistakes:

• Confusing SUBSCRIBE with deleting or saving data
• Thinking SUBSCRIBE lists keys
• Assuming SUBSCRIBE modifies data

2. Which of the following is the correct syntax to subscribe to channels 'news' and 'sports' in Redis CLI?

easy

A. SUBSCRIBE('news', 'sports')

B. SUBSCRIBE news sports

C. subscribe news, sports

D. SUBSCRIBE TO news AND sports

Solution

1. Step 1: Recall Redis CLI command format

   Redis commands are typed in uppercase followed by arguments separated by spaces.

2. Step 2: Match syntax with options

   SUBSCRIBE news sports matches the correct Redis CLI syntax: SUBSCRIBE news sports. Other options use incorrect syntax or punctuation.

3. Final Answer:

   SUBSCRIBE news sports -> Option B

4. Quick Check:

   Correct Redis CLI syntax = SUBSCRIBE news sports [OK]

Hint: Use uppercase command and space-separated channels [OK]

Common Mistakes:

• Using parentheses like a function call
• Adding commas between channels
• Using extra keywords like TO or AND

3. You want to listen to messages from channels 'chat', 'alerts', and 'updates' simultaneously. Which Redis command should you use to subscribe to all three channels at once?

easy

A. SUBSCRIBE [chat alerts updates]

B. SUBSCRIBE chat; SUBSCRIBE alerts; SUBSCRIBE updates

C. SUBSCRIBE TO chat, alerts, updates

D. SUBSCRIBE chat alerts updates

Solution

1. Step 1: Recall how to subscribe to multiple channels

   Redis SUBSCRIBE accepts multiple channel names separated by spaces in one command.

2. Step 2: Evaluate options for correctness

   SUBSCRIBE chat alerts updates uses correct syntax: SUBSCRIBE chat alerts updates. Other options use invalid syntax or multiple commands unnecessarily.

3. Final Answer:

   SUBSCRIBE chat alerts updates -> Option D

4. Quick Check:

   One SUBSCRIBE with multiple channels = SUBSCRIBE chat alerts updates [OK]

Hint: List all channels after SUBSCRIBE separated by spaces [OK]

Common Mistakes:

• Using commas or brackets in channel list
• Trying multiple SUBSCRIBE commands instead of one
• Adding extra keywords like TO

4. What will happen if a client executes the following Redis commands?

SUBSCRIBE sports
PUBLISH sports "Game tonight!"

medium

A. An error occurs because PUBLISH cannot be used after SUBSCRIBE

B. The client publishes the message but does not receive it

C. The client receives the message "Game tonight!" on the 'sports' channel

D. The client unsubscribes from the 'sports' channel

Solution

1. Step 1: Understand SUBSCRIBE effect

   After SUBSCRIBE sports, the client enters pub/sub mode where it can receive messages published to subscribed channels.

2. Step 2: Check PUBLISH behavior

   PUBLISH can be executed by any client, including the one subscribed. The client will receive the message "Game tonight!" on the 'sports' channel.

3. Final Answer:

   The client receives the message "Game tonight!" on the 'sports' channel -> Option C

4. Quick Check:

   SUBSCRIBE then PUBLISH = client receives message [OK]

Hint: After SUBSCRIBE, client receives published messages on subscribed channels [OK]

Common Mistakes:

• Thinking PUBLISH works and client receives own message
• Assuming PUBLISH succeeds but client doesn't receive
• Believing PUBLISH causes unsubscribe

5. A developer runs this Redis command: SUBSCRIBE without any channel names. What is the result?

medium

A. Syntax error: SUBSCRIBE requires at least one channel

B. The client unsubscribes from all channels

C. The client subscribes to all channels

D. The command is ignored and no subscription happens

Solution

1. Step 1: Check SUBSCRIBE command requirements

   SUBSCRIBE must be followed by at least one channel name to subscribe to.

2. Step 2: Identify error from missing arguments

   Running SUBSCRIBE alone causes a syntax error because no channels are specified.

3. Final Answer:

   Syntax error: SUBSCRIBE requires at least one channel -> Option A

4. Quick Check:

   SUBSCRIBE needs channels = syntax error if missing [OK]

Hint: SUBSCRIBE needs channels; missing channels cause syntax error [OK]

Common Mistakes:

• Assuming SUBSCRIBE with no args subscribes to all channels
• Thinking it unsubscribes instead
• Believing command is ignored silently