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.