Redis connection and basic commands in Azure - Step-by-Step Execution

Process Flow - Redis connection and basic commands

Start Redis Client Setup

↓

Connect to Redis Server

↓

Send Command: SET key value

↓

Receive Response: OK

↓

Send Command: GET key

↓

Receive Response: value

↓

Close Connection

This flow shows connecting to Redis, setting a key-value pair, getting the value, and closing the connection.

Execution Sample

Azure

redis_client = connect_to_redis('hostname', port)
redis_client.set('color', 'blue')
value = redis_client.get('color')
print(value)
redis_client.close()

Connects to Redis, sets 'color' to 'blue', retrieves it, prints it, then closes connection.

Process Table

Step	Action	Command Sent	Response Received	State Change
1	Connect to Redis server	CONNECT	CONNECTED	Client connected to Redis server
2	Set key 'color' to 'blue'	SET color blue	OK	Key 'color' stored with value 'blue'
3	Get value of key 'color'	GET color	"blue"	Value 'blue' retrieved for key 'color'
4	Print value	N/A	"blue"	Output 'blue' displayed
5	Close connection	DISCONNECT	DISCONNECTED	Client disconnected from Redis server

💡 Connection closed after commands executed successfully

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
redis_client	null	connected	connected	connected	closed
value	null	null	"blue"	"blue"	"blue"

Key Moments - 3 Insights

Why do we get 'OK' after the SET command?

Redis replies 'OK' to confirm the key-value pair was stored successfully, as shown in step 2 of the execution_table.

What happens if we try to GET a key that does not exist?

Redis returns a null or empty response, meaning no value found. This is different from step 3 where 'blue' was returned.

Why must we close the connection after commands?

Closing frees resources and ends the session cleanly, as shown in step 5 where the client disconnects.

Visual Quiz - 3 Questions

Look at the execution_table, what response does Redis give after the SET command?

A "OK"

B "blue"

C "CONNECTED"

D "DISCONNECTED"

💡 Hint

Check step 2 in the execution_table under 'Response Received'

At which step does the client retrieve the value 'blue' from Redis?

A Step 4

B Step 1

C Step 3

D Step 5

💡 Hint

Look at the 'Response Received' column in the execution_table for the value 'blue'

If the connection was not closed, what would be the state of redis_client after step 5?

A "closed"

B "connected"

C "null"

D "error"

💡 Hint

Refer to variable_tracker for redis_client state after each step

Concept Snapshot

Redis connection and commands:
1. Connect to Redis server.
2. Use SET to store key-value pairs.
3. Use GET to retrieve values by key.
4. Redis replies 'OK' for successful SET.
5. Close connection to free resources.

Full Transcript

This lesson shows how to connect to a Redis server, set a key-value pair, get the value back, and close the connection. First, the client connects to Redis. Then it sends a SET command to store 'color' with value 'blue'. Redis replies with 'OK' confirming storage. Next, the client sends a GET command for 'color' and receives 'blue'. The value is printed. Finally, the client closes the connection to end the session cleanly. Variables track the connection state and stored value throughout. This step-by-step trace helps beginners see exactly what happens during Redis commands.

Practice

1. What is the main purpose of Redis in cloud applications?

easy

A. To store data in memory for fast access

B. To provide long-term file storage

C. To manage user authentication

D. To host web pages

Solution

1. Step 1: Understand Redis data storage

   Redis stores data in memory, which makes data access very fast compared to disk storage.

2. Step 2: Compare Redis purpose with options

   Options B, C, and D describe other services, but Redis is mainly for fast in-memory data storage.

3. Final Answer:

   To store data in memory for fast access -> Option A

4. Quick Check:

   Redis = fast in-memory storage [OK]

Hint: Remember Redis is all about speed using memory [OK]

Common Mistakes:

• Confusing Redis with file storage
• Thinking Redis manages user login
• Assuming Redis hosts websites

2. Which of the following is the correct way to connect to an Azure Redis Cache instance using a connection string?

easy

A. redis.connect('hostname,port,password=yourPassword')

B. redis.connect('hostname;port;password=yourPassword')

C. redis.connect('hostname:port,password=yourPassword')

D. redis.connect('hostname port password yourPassword')

Solution

1. Step 1: Recall Redis connection string format

   The correct format uses colon ':' to separate hostname and port, and comma ',' to separate parameters like password.

2. Step 2: Match options with correct format

   redis.connect('hostname:port,password=yourPassword') uses 'hostname:port,password=yourPassword' which is the standard format. Others use wrong separators.

3. Final Answer:

   redis.connect('hostname:port,password=yourPassword') -> Option C

4. Quick Check:

   Use ':' for host-port and ',' for parameters [OK]

Hint: Use ':' between host and port, ',' before password [OK]

Common Mistakes:

• Using semicolons instead of commas
• Separating host and port with commas
• Leaving out password parameter

3. Given the following Redis commands executed in order:

SET counter 5
INCR counter
GET counter

What will be the output of the last command?

medium

A. 5

B. Error

C. 7

D. 6

Solution

1. Step 1: Analyze the SET command

   SET counter 5 stores the string '5' as the value of key 'counter'.

2. Step 2: Analyze the INCR command

   INCR increases the numeric value of 'counter' by 1, changing it from 5 to 6.

3. Step 3: Analyze the GET command

   GET counter retrieves the current value, which is now 6.

4. Final Answer:

   6 -> Option D

5. Quick Check:

   SET 5 + INCR = 6 [OK]

Hint: INCR adds 1 to the stored number [OK]

Common Mistakes:

• Thinking INCR adds 2
• Assuming GET returns original value
• Expecting an error on INCR

4. You run the command INCR mykey on a Redis key that does not exist. What happens?

medium

A. Redis returns an error because the key is missing

B. Redis creates the key with value 1

C. Redis creates the key with value 0

D. Redis ignores the command

Solution

1. Step 1: Understand INCR behavior on missing keys

   When INCR is called on a key that does not exist, Redis treats it as 0 before incrementing.

2. Step 2: Result of INCR on missing key

   Redis creates the key with value 1 after incrementing from 0.

3. Final Answer:

   Redis creates the key with value 1 -> Option B

4. Quick Check:

   INCR on missing key sets it to 1 [OK]

Hint: INCR on missing key starts at 1 automatically [OK]

Common Mistakes:

• Expecting an error on missing key
• Thinking key is set to 0
• Assuming command is ignored

5. You want to store a user's login count in Azure Redis and increase it each time they log in. Which sequence of commands correctly achieves this without errors?

hard

A. SET loginCount 0INCR loginCountGET loginCount

B. INCR loginCountSET loginCount 0GET loginCount

C. GET loginCountINCR loginCountSET loginCount 0

D. SET loginCount 'zero'INCR loginCountGET loginCount

Solution

1. Step 1: Initialize loginCount properly

   Using SET loginCount 0 sets the key to a numeric string '0', ready for increment.

2. Step 2: Increment and retrieve value

   INCR loginCount increases the count to 1, then GET loginCount returns the updated count.

3. Step 3: Analyze incorrect options

   INCR loginCount
   SET loginCount 0
   GET loginCount increments before setting, which works but is less clear. GET loginCount
   INCR loginCount
   SET loginCount 0 gets before setting, may return null. SET loginCount 'zero'
   INCR loginCount
   GET loginCount sets a non-numeric string, causing INCR to error.

4. Final Answer:

   SET loginCount 0
   INCR loginCount
   GET loginCount -> Option A

5. Quick Check:

   Initialize numeric before INCR to avoid errors [OK]

Hint: Always set numeric string before INCR to avoid errors [OK]

Common Mistakes:

• Incrementing before setting initial value
• Setting non-numeric string before INCR
• Getting value before initialization