SET and GET commands in Redis - Deep Dive

Overview - SET and GET commands

What is it?

SET and GET are basic commands in Redis, a fast in-memory database. SET stores a value with a key, like putting a label on a box. GET retrieves the value using the key, like finding the box by its label. These commands let you save and find data quickly.

Why it matters

Without SET and GET, Redis couldn't store or retrieve data, making it useless as a database. They solve the problem of fast data access, which is crucial for apps like caching, real-time analytics, and session storage. Without them, apps would be slower and less responsive.

Where it fits

Before learning SET and GET, you should understand what a key-value store is and basic command-line usage. After mastering these, you can learn about data expiration, advanced data types, and transactions in Redis.

Mental Model

Core Idea

SET saves a value with a name, and GET finds the value by that name instantly.

Think of it like...

It's like writing a note and putting it in a labeled envelope (SET), then later finding the envelope by its label to read the note (GET).

┌───────────┐       ┌───────────────┐
│   SET     │──────▶│ Store key-value│
│ (key, val)│       │ pair in memory │
└───────────┘       └───────────────┘
      ▲                     │
      │                     ▼
┌───────────┐       ┌───────────────┐
│   GET     │◀─────│ Retrieve value │
│ (key)     │       │ by key        │
└───────────┘       └───────────────┘

Build-Up - 7 Steps

1

Foundation

Understanding Redis Key-Value Storage

Concept: Redis stores data as key-value pairs, where each key is unique and points to a value.

Imagine a dictionary where each word (key) has a definition (value). Redis works similarly but stores these pairs in memory for fast access.

Result

You know that Redis organizes data by unique keys linked to values.

Understanding the key-value model is essential because SET and GET operate directly on these pairs.

2

Foundation

Basic Syntax of SET and GET

Concept: Learn the exact commands to store and retrieve data in Redis.

To store data: SET key value To retrieve data: GET key Example: SET name "Alice" GET name

Result

The value 'Alice' is stored under 'name' and can be retrieved instantly.

Knowing the simple syntax lets you interact with Redis immediately and see how data is saved and fetched.

3

Intermediate

Handling Missing Keys with GET

🤔Before reading on: What do you think GET returns if the key does not exist? Null, error, or empty string? Commit to your answer.

Concept: GET returns a special 'nil' response if the key is missing, not an error or empty string.

If you try GET on a key that was never set or was deleted, Redis replies with (nil), meaning no value found.

Result

You learn to check for (nil) to handle missing data gracefully in your app.

Knowing GET's behavior on missing keys prevents bugs and helps design robust data retrieval logic.

4

Intermediate

Overwriting Values with SET

🤔Before reading on: Does SET add a new key or overwrite existing keys? Commit to your answer.

Concept: SET replaces the value if the key already exists, updating the stored data.

If you run SET name "Bob" after SET name "Alice", the value for 'name' changes to 'Bob'.

Result

You understand that SET is both for creating and updating data.

Knowing SET overwrites helps avoid unexpected data loss and supports updating stored information.

5

Intermediate

Using SET with Expiration Time

🤔Before reading on: Can SET make data disappear automatically after some time? Commit to your answer.

Concept: SET can store data with a time limit, after which Redis deletes it automatically.

Example: SET session "abc123" EX 10 This stores 'session' with value 'abc123' that expires in 10 seconds.

Result

You can create temporary data like sessions or caches that clean up themselves.

Understanding expiration with SET enables efficient memory use and automatic data lifecycle management.

6

Advanced

Atomicity and Performance of SET and GET

🤔Before reading on: Are SET and GET operations atomic and fast? Commit to your answer.

Concept: SET and GET are atomic commands executed fully or not at all, ensuring data consistency and very high speed.

Redis processes each command sequentially in a single thread, so SET and GET never interfere with each other or partial updates.

Result

You gain confidence that data won't be corrupted by concurrent access and that Redis is extremely fast.

Knowing atomicity and performance characteristics helps design reliable and scalable systems using Redis.

7

Expert

Internal Memory Storage and Command Optimization

🤔Before reading on: Do you think Redis stores keys and values as plain strings or uses special memory structures? Commit to your answer.

Concept: Redis stores keys and values in optimized memory structures for speed and low overhead, and commands like SET/GET are optimized at the C code level.

Internally, Redis uses a hash table for keys and stores values as raw bytes or encoded forms. SET updates the hash table quickly, and GET fetches values with minimal CPU cycles.

Result

You understand why Redis is so fast and how it manages memory efficiently.

Knowing internal storage and optimization reveals why Redis outperforms many databases and guides advanced tuning.

Under the Hood

Redis keeps all data in memory using a hash table where keys map to values. When you run SET, Redis inserts or updates the key in this table. GET looks up the key in the table and returns the value if found. Commands run sequentially in a single thread, avoiding race conditions. Expiration times are tracked separately and checked periodically.

Why designed this way?

Redis was designed for speed and simplicity. Using in-memory storage and a single-threaded event loop avoids complex locking and context switching. This design trades off persistence durability for performance but can be combined with snapshots or append-only files for durability.

┌───────────────┐
│ Client sends  │
│ SET or GET    │
└──────┬────────┘
       │
┌──────▼────────┐
│ Redis Server  │
│ Single-thread │
│ Event Loop    │
└──────┬────────┘
       │
┌──────▼────────┐
│ In-memory     │
│ Hash Table   │
│ (key → value) │
└───────────────┘

Myth Busters - 4 Common Misconceptions

Quick: Does GET return an error if the key does not exist? Commit yes or no.

Common Belief: GET returns an error if the key is missing.

Reality: GET returns a special nil value, not an error, when the key is absent.

Why it matters: Expecting an error can cause unnecessary error handling and confusion in application code.

Quick: Does SET add a new key only or overwrite existing keys? Commit your answer.

Common Belief: SET only adds new keys and fails if the key exists.

Reality: SET overwrites the value if the key already exists without error.

Why it matters: Misunderstanding this can lead to accidental data loss when updating keys.

Quick: Does SET with expiration guarantee exact deletion time? Commit yes or no.

Common Belief: SET with expiration deletes keys exactly at the specified time.

Reality: Expiration is approximate; Redis checks expirations periodically, so deletion may be slightly delayed.

Why it matters: Relying on exact expiration timing can cause subtle bugs in time-sensitive applications.

Quick: Is Redis multi-threaded internally for SET and GET? Commit yes or no.

Common Belief: Redis uses multiple threads to handle SET and GET commands concurrently.

Reality: Redis processes commands in a single thread to ensure atomicity and simplicity.

Why it matters: Assuming multi-threading can lead to incorrect assumptions about concurrency and data races.

Expert Zone

1

SET can be combined with NX or XX options to set keys conditionally, which is useful for locking or updating only existing keys.

2

GET is a simple command but can be pipelined with others to reduce network latency in batch operations.

3

Expiration times set by SET EX are stored separately and do not affect the key's value encoding or retrieval speed.

When NOT to use

SET and GET are not suitable for storing complex data structures directly; use Redis data types like hashes, lists, or sets instead. For persistent storage with complex queries, use a traditional database like PostgreSQL or MongoDB.

Production Patterns

In production, SET and GET are often used for caching database query results, session management, and feature flags. They are combined with expiration to automatically clean stale data and with conditional SET to implement distributed locks.

Connections

Hash Tables

SET and GET operations build on the hash table data structure for fast key lookup.

Understanding hash tables explains why Redis commands are so fast and how collisions are handled internally.

HTTP Caching

Redis SET with expiration is similar to HTTP cache-control headers that specify how long data is valid.

Knowing HTTP caching helps understand why and how Redis expires keys to keep data fresh.

Memory Management

Redis stores all data in RAM, so SET and GET performance depends on efficient memory use.

Understanding memory management helps optimize Redis usage and avoid out-of-memory errors.

Common Pitfalls

#1 Trying to GET a key that does not exist and expecting a string result.

Wrong approach:

GET missing_key

Correct approach:

Check if GET returns (nil) before using the value.

Root cause:

Misunderstanding that GET returns nil, not an error or empty string, leads to runtime errors.

#2 Using SET without expiration for session data that should expire.

Wrong approach:

SET session_id abc123

Correct approach:

SET session_id abc123 EX 3600

Root cause:

Forgetting to set expiration causes stale data to accumulate and waste memory.

#3 Assuming SET will fail if the key exists and using it for locking.

Wrong approach:

SET lock_key 1

Correct approach:

SET lock_key 1 NX EX 10

Root cause:

Not using NX option causes overwriting locks, breaking mutual exclusion guarantees.

Key Takeaways

SET stores a value by key, and GET retrieves it instantly from Redis memory.

GET returns nil for missing keys, not an error or empty string.

SET overwrites existing keys unless used with options like NX or XX.

SET can set expiration times to automatically delete keys after a period.

Redis processes SET and GET atomically and very fast using an in-memory hash table.

Practice

1. What does the Redis SET command do?

easy

A. Retrieves a value by key

B. Stores a value with a specified key

C. Deletes a key and its value

D. Lists all keys in the database

Solution

1. Step 1: Understand the purpose of SET

   The SET command in Redis is used to save or store a value associated with a key.

2. Step 2: Compare with other commands

   GET retrieves values, DEL deletes keys, and KEYS lists keys, so they are not correct here.

3. Final Answer:

   Stores a value with a specified key -> Option B

4. Quick Check:

   SET saves data = A [OK]

Hint: SET saves data by key, GET fetches it [OK]

Common Mistakes:

• Confusing SET with GET
• Thinking SET deletes data
• Mixing SET with key listing

2. Which of the following is the correct syntax to store the value "hello" with the key "greeting" in Redis?

easy

A. SET greeting hello

B. GET greeting hello

C. SET "greeting" "hello"

D. SET greeting, hello

Solution

1. Step 1: Recall Redis SET syntax

   The correct syntax is SET key value without commas or quotes unless the shell requires them.

2. Step 2: Analyze options

   SET greeting hello matches the correct syntax. GET greeting hello uses GET which is wrong. SET "greeting" "hello" uses quotes unnecessarily. SET greeting, hello uses a comma which is invalid.

3. Final Answer:

   SET greeting hello -> Option A

4. Quick Check:

   SET key value no commas [OK]

Hint: Use SET key value without commas or quotes [OK]

Common Mistakes:

• Using GET instead of SET
• Adding commas between arguments
• Unnecessary quotes around key/value

3. Given the following Redis commands executed in order:

SET color blue
GET color
SET color red
GET color

What will be the output of the two GET commands?

medium

A. "blue" and then "red"

B. "red" and then "blue"

C. "blue" and then "blue"

D. nil and then "red"

Solution

1. Step 1: Analyze the first SET and GET

   The first SET color blue stores "blue". The first GET color returns "blue".

2. Step 2: Analyze the second SET and GET

   The second SET color red overwrites the value with "red". The second GET color returns "red".

3. Final Answer:

   "blue" and then "red" -> Option A

4. Quick Check:

   SET overwrites value, GET returns current value [OK]

Hint: SET overwrites; GET returns latest value [OK]

Common Mistakes:

• Assuming GET returns old value
• Thinking SET appends values
• Expecting nil on first GET

4. You run the command GET username but get a nil response. Which of the following could fix this issue?

medium

A. Run GET username again immediately

B. Use DEL username before GET

C. Restart the Redis server

D. Run SET username "guest" before GET

Solution

1. Step 1: Understand nil response from GET

   Nil means the key "username" does not exist or has no value stored.

2. Step 2: Fix by setting a value

   To get a value, you must first store it using SET username "guest". Other options do not create the key.

3. Final Answer:

   Run SET username "guest" before GET -> Option D

4. Quick Check:

   Nil means no key; SET creates it [OK]

Hint: Nil means missing key; SET it first [OK]

Common Mistakes:

• Retrying GET without SET
• Deleting key before GET
• Restarting server unnecessarily

5. You want to store a user's session token in Redis with key "session:123" and value "abc123token". Which sequence of commands correctly stores and retrieves this token?

hard

A. SET session:123 abc123token
DEL session:123
GET session:123

B. GET session:123
SET session:123 abc123token

C. SET session:123 abc123token
GET session:123

D. SET "session:123" "abc123token"
DEL session:123
GET session:123

Solution

1. Step 1: Store the session token

   Use SET session:123 abc123token to save the token under the key.

2. Step 2: Retrieve the stored token

   Use GET session:123 to fetch the token value.

3. Step 3: Analyze other options

   GET session:123 SET session:123 abc123token tries to GET before SET, so returns nil. Options A and C delete the key before GET, so GET returns nil.

4. Final Answer:

   SET session:123 abc123token GET session:123 -> Option C

5. Quick Check:

   SET then GET returns stored value [OK]

Hint: Always SET before GET to retrieve stored data [OK]

Common Mistakes:

• GET before SET returns nil
• Deleting key before GET
• Using quotes unnecessarily