Redis connection and basic commands in Azure - Commands & Configuration

Introduction

Redis is a fast database that stores data in memory. It helps apps remember information quickly. You connect to Redis and use simple commands to save and get data.

When you want to store user session data for a web app to keep users logged in.

When you need to count how many times something happens, like page views.

When you want to cache data to make your app faster by avoiding slow database calls.

When you want to share data between different parts of your app quickly.

When you need a simple message queue to pass messages between services.

Commands

Connect to the Azure Redis Cache instance securely using TLS with the hostname, port, and password.

Terminal

redis-cli -h redis-example.redis.cache.windows.net -p 6380 -a MyStrongPassword --tls

Expected Output

redis-example.redis.cache.windows.net:6380> 

→

-h - Specifies the Redis server hostname.

→

-p - Specifies the port number to connect to.

→

--tls - Enables secure TLS connection.

Store the text "Hello, Redis!" under the key named 'greeting'.

Terminal

SET greeting "Hello, Redis!"

Expected Output

OK

Retrieve the value stored under the key 'greeting'.

Terminal

GET greeting

Expected Output

Hello, Redis!

Increase the number stored under 'page_views' by 1. If it doesn't exist, Redis starts it at 0 then adds 1.

Terminal

INCR page_views

Expected Output

1

Set the key 'greeting' to expire and be deleted after 60 seconds.

Terminal

EXPIRE greeting 60

Expected Output

1

Key Concept

If you remember nothing else, remember: Redis stores data as keys and values that you can set, get, and update instantly.

Common Mistakes

Trying to connect without the --tls flag to Azure Redis Cache.

Azure Redis requires secure TLS connections on port 6380, so the connection will fail without it.

Always include --tls when connecting to Azure Redis on port 6380.

Using GET on a key that does not exist.

Redis returns (nil) which might be confusing if not handled properly in your app.

Check if the returned value is nil before using it.

Using INCR on a key that holds a non-integer value.

Redis will return an error because it cannot increment non-numeric values.

Ensure the key is either not set or holds an integer before using INCR.

Summary

Use redis-cli with hostname, port, password, and --tls to connect securely to Azure Redis Cache.

Use SET to save data and GET to retrieve it by key.

Use INCR to count things and EXPIRE to set automatic deletion times.

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