Memorystore for Redis caching in GCP - Mini Project: Build & Apply

Memorystore for Redis caching

📖 Scenario: You are building a simple caching layer for a web application hosted on Google Cloud Platform. To speed up data retrieval, you want to use Memorystore for Redis, a managed Redis service. This project will guide you through creating a Redis instance, configuring it, and preparing it for use.

🎯 Goal: Create a Memorystore for Redis instance with basic configuration to enable caching for your application.

📋 What You'll Learn

Create a Redis instance with a specific name and tier

Set the Redis memory size

Configure the Redis instance with a region and authorized network

Enable Redis persistence

💡 Why This Matters

🌍 Real World

Memorystore for Redis is used to speed up applications by caching frequently accessed data, reducing database load and improving response times.

💼 Career

Cloud engineers and developers often configure managed Redis instances to optimize application performance and reliability in production environments.

1

Create a Redis instance dictionary

Create a dictionary called redis_instance with these exact keys and values: 'name': 'my-redis-cache', 'tier': 'STANDARD_HA', and 'memory_size_gb': 4.

GCP

# Create the redis_instance dictionary with name, tier, and memory_size_gb
# Your code here

Hint

Use a Python dictionary with the exact keys and values as specified.

2

Add region and authorized network configuration

Add two new keys to the redis_instance dictionary: 'region' with value 'us-central1' and 'authorized_network' with value 'default'.

GCP

redis_instance = {
    'name': 'my-redis-cache',
    'tier': 'STANDARD_HA',
    'memory_size_gb': 4
}
# Add 'region' and 'authorized_network' keys to redis_instance
# Your code here

Hint

Add the new keys directly inside the existing dictionary.

3

Enable Redis persistence

Add a key 'persistence_config' to the redis_instance dictionary with a nested dictionary value containing 'persistence_enabled': true.

GCP

redis_instance = {
    'name': 'my-redis-cache',
    'tier': 'STANDARD_HA',
    'memory_size_gb': 4,
    'region': 'us-central1',
    'authorized_network': 'default'
}
# Add 'persistence_config' with 'persistence_enabled': true
# Your code here

Hint

Use a nested dictionary for the persistence configuration.

4

Add Redis version and complete configuration

Add a key 'redis_version' with value 'REDIS_6_X' to the redis_instance dictionary to specify the Redis version.

GCP

redis_instance = {
    'name': 'my-redis-cache',
    'tier': 'STANDARD_HA',
    'memory_size_gb': 4,
    'region': 'us-central1',
    'authorized_network': 'default',
    'persistence_config': {
        'persistence_enabled': True
    }
}
# Add 'redis_version' key with value 'REDIS_6_X'
# Your code here

Hint

Specify the Redis version as a string in the dictionary.

Practice

1. What is the main purpose of Memorystore for Redis in Google Cloud?

easy

A. To run virtual machines

B. To permanently store large files

C. To temporarily store data to speed up applications

D. To manage user authentication

Solution

1. Step 1: Understand Memorystore for Redis role

   Memorystore for Redis is designed to cache data temporarily to improve app speed.

2. Step 2: Compare options with purpose

   Options A, B, and D describe unrelated services or functions.

3. Final Answer:

   To temporarily store data to speed up applications -> Option C

4. Quick Check:

   Memorystore caches data = C [OK]

Hint: Memorystore caches data temporarily to speed apps [OK]

Common Mistakes:

• Confusing caching with permanent storage
• Thinking it manages VMs or authentication
• Assuming it stores large files permanently

2. Which of the following is the correct command snippet to create a Memorystore Redis instance with 1 GB memory in region us-central1?

easy

A. gcloud redis create instance my-redis --memory=1GB --region=us-central1

B. gcloud redis instances create my-redis --size=1 --region=us-central1

C. gcloud redis instances create my-redis --memory=1GB --zone=us-central1-a

D. gcloud redis instances new my-redis --size=1GB --region=us-central1

Solution

1. Step 1: Recall correct gcloud command syntax

   The correct command uses 'gcloud redis instances create' with '--size' in GB and '--region'.

2. Step 2: Check each option for syntax errors

   gcloud redis instances create my-redis --size=1 --region=us-central1 matches correct syntax. Options A, C, and D use wrong flags or commands.

3. Final Answer:

   gcloud redis instances create my-redis --size=1 --region=us-central1 -> Option B

4. Quick Check:

   Correct gcloud create syntax = B [OK]

Hint: Use 'gcloud redis instances create' with --size and --region [OK]

Common Mistakes:

• Using --memory instead of --size
• Using 'create instance' instead of 'instances create'
• Specifying zone instead of region

3. Given this Python code snippet using Redis client connected to Memorystore, what will be printed?

import redis
client = redis.Redis(host='10.0.0.5', port=6379)
client.set('color', 'blue')
print(client.get('color'))

medium

A. None

B. 'blue'

C. blue

D. b'blue'

Solution

1. Step 1: Understand Redis get returns bytes

   Redis client returns values as bytes, so 'client.get' returns b'blue'.

2. Step 2: Check print output

   Printing bytes shows with b'' prefix, so output is b'blue'.

3. Final Answer:

   b'blue' -> Option D

4. Quick Check:

   Redis get returns bytes = b'blue' [OK]

Hint: Redis get returns bytes, not string [OK]

Common Mistakes:

• Expecting plain string instead of bytes
• Confusing Redis set/get syntax
• Assuming None if key exists

4. You created a Memorystore Redis instance but your app cannot connect. Which is the most likely cause?

medium

A. The Redis instance is in a different VPC network than the app

B. The Redis instance size is too small

C. The Redis instance region is the same as the app

D. The Redis instance is running the wrong Redis version

Solution

1. Step 1: Identify common connectivity issues

   Memorystore requires the app and Redis instance to be in the same VPC or connected networks.

2. Step 2: Evaluate options

   The Redis instance is in a different VPC network than the app correctly identifies network mismatch causing connection failure. Size, region, or version mismatches do not block connection.

3. Final Answer:

   The Redis instance is in a different VPC network than the app -> Option A

4. Quick Check:

   Network mismatch blocks connection = A [OK]

Hint: Check VPC network match for app and Redis [OK]

Common Mistakes:

• Blaming size or region for connection failure
• Ignoring network setup
• Assuming version mismatch blocks connection

5. You want to reduce database load by caching user session data using Memorystore for Redis. Which approach is best to ensure sessions expire automatically after 30 minutes?

hard

A. Set a TTL (time-to-live) of 1800 seconds on each session key when storing it

B. Manually delete session keys every 30 minutes using a cron job

C. Use a Redis instance with a 30-minute auto-shutdown setting

D. Store sessions without expiration and rely on database cleanup

Solution

1. Step 1: Understand session expiration in Redis

   Redis supports TTL on keys to expire them automatically after a set time.

2. Step 2: Evaluate options for automatic expiration

   Set a TTL (time-to-live) of 1800 seconds on each session key when storing it uses TTL correctly. Manually delete session keys every 30 minutes using a cron job is manual and error-prone. Use a Redis instance with a 30-minute auto-shutdown setting is invalid Redis feature. Store sessions without expiration and rely on database cleanup does not expire sessions.

3. Final Answer:

   Set a TTL (time-to-live) of 1800 seconds on each session key when storing it -> Option A

4. Quick Check:

   Use TTL for auto-expire sessions = D [OK]

Hint: Use TTL on keys for automatic expiration [OK]

Common Mistakes:

• Relying on manual deletion
• Expecting Redis instance to auto-shutdown
• Not setting expiration causing stale sessions