Transactions vs Lua scripts in Redis - When to Use Which

The Big Idea

What if your inventory updates could never get mixed up, no matter how many customers buy at once?

The Scenario

Imagine you are managing a busy online store's inventory. You try to update stock counts manually by sending multiple separate commands to the database for each item sold.

Sometimes, two updates happen at the same time, causing confusion and wrong stock numbers.

The Problem

Manually sending separate commands can cause errors because the database might process them out of order or interrupt one update with another.

This leads to inconsistent data, lost updates, and frustrated customers.

The Solution

Using transactions or Lua scripts lets you bundle multiple commands into one atomic operation.

This means all commands run together without interruption, keeping your data accurate and safe.

Before vs After

✗ Before

SET stock 10
INCRBY stock -1
GET stock

✓ After

MULTI
DECR stock
EXEC
-- or --
EVAL 'redis.call("DECR", KEYS[1])' 1 stock

What It Enables

It enables safe, reliable updates to your data even when many users act at the same time.

Real Life Example

When many customers buy the same product simultaneously, transactions or Lua scripts ensure the stock count never goes below zero and reflects true availability.

Key Takeaways

Manual separate commands risk data errors under concurrent use.

Transactions group commands to run safely together.

Lua scripts allow custom logic to run atomically inside the database.

Practice

1. What is the main difference between Redis transactions and Lua scripts?

easy

A. Transactions run commands one by one, Lua scripts run commands outside Redis.

B. Transactions group commands to run atomically, Lua scripts run complex logic atomically inside Redis.

C. Transactions can only read data, Lua scripts can only write data.

D. Transactions are faster than Lua scripts in all cases.

Solution

1. Step 1: Understand Redis transactions

   Transactions group multiple commands to run atomically, meaning all commands succeed or none do.

2. Step 2: Understand Lua scripts in Redis

   Lua scripts run inside Redis and can include complex logic, running atomically as a single operation.

3. Final Answer:

   Transactions group commands to run atomically, Lua scripts run complex logic atomically inside Redis. -> Option B

4. Quick Check:

   Transactions vs Lua scripts = Grouped commands vs complex logic [OK]

Hint: Transactions group commands; Lua scripts add logic inside Redis [OK]

Common Mistakes:

• Thinking Lua scripts run outside Redis
• Believing transactions can only read or write
• Assuming transactions are always faster

2. Which of the following is the correct way to start a Redis transaction?

easy

A. EXEC

B. START TRANSACTION

C. BEGIN

D. MULTI

Solution

1. Step 1: Recall Redis transaction commands

   Redis uses the command MULTI to start a transaction block.

2. Step 2: Identify the correct command

   START TRANSACTION and BEGIN are SQL commands, not Redis. EXEC ends the transaction.

3. Final Answer:

   MULTI -> Option D

4. Quick Check:

   Start Redis transaction = MULTI [OK]

Hint: Use MULTI to start Redis transactions, EXEC to finish [OK]

Common Mistakes:

• Using SQL commands like START TRANSACTION
• Confusing EXEC as start command
• Using BEGIN which is not Redis syntax

3. Given this Lua script in Redis:

local current = redis.call('GET', KEYS[1])
if not current then
  redis.call('SET', KEYS[1], ARGV[1])
  return ARGV[1]
else
  return current
end

What will be the output if the key does not exist and ARGV[1] is "100"?

medium

A. Error

B. nil

C. "100"

D. "0"

Solution

1. Step 1: Analyze the Lua script logic

   The script checks if the key exists. If not, it sets the key to ARGV[1] and returns ARGV[1].

2. Step 2: Apply the input values

   Since the key does not exist, it sets the key to "100" and returns "100".

3. Final Answer:

   "100" -> Option C

4. Quick Check:

   Key missing sets and returns ARGV[1] = "100" [OK]

Hint: If key missing, Lua sets and returns ARGV[1] [OK]

Common Mistakes:

• Assuming nil is returned when key missing
• Expecting an error from redis.call
• Confusing return values with zero

4. You wrote this Redis transaction:

MULTI
SET key1 foo
INCR key1
EXEC

But the INCR command fails with an error. What is the likely cause?

medium

A. SET sets key1 as a string, INCR expects an integer value

B. INCR cannot be used inside MULTI blocks

C. EXEC was missing to run the transaction

D. MULTI command syntax is incorrect

Solution

1. Step 1: Understand SET and INCR behavior

   SET stores the value as a string. INCR expects the key to hold an integer value.

2. Step 2: Identify the error cause

   Since SET sets "foo" as a string, INCR fails because it cannot increment a non-integer string.

3. Final Answer:

   SET sets key1 as a string, INCR expects an integer value -> Option A

4. Quick Check:

   INCR needs integer, SET stores string [OK]

Hint: INCR needs integer; SET stores string by default [OK]

Common Mistakes:

• Thinking INCR can't be in MULTI
• Forgetting to EXEC the transaction
• Assuming MULTI syntax is wrong

5. You want to atomically check if a key exists and increment it only if it does, otherwise set it to 1. Which approach is best in Redis?

hard

A. Use a Lua script that checks and updates the key atomically

B. Use Redis pipeline to send GET and INCR commands together

C. Run separate GET and INCR commands without transactions

D. Use a Redis transaction with WATCH, GET, and MULTI commands

Solution

1. Step 1: Understand the atomicity requirement

   The operation must be atomic: check existence and update in one step without race conditions.

2. Step 2: Compare approaches

   Transactions with WATCH can be complex and may fail due to race conditions. Separate commands or pipelines are not atomic. Lua scripts run atomically inside Redis and can handle logic safely.

3. Final Answer:

   Use a Lua script that checks and updates the key atomically -> Option A

4. Quick Check:

   Atomic check and update = Lua script [OK]

Hint: Use Lua scripts for atomic logic beyond simple transactions [OK]

Common Mistakes:

• Assuming WATCH transactions are always safe
• Using separate commands risking race conditions
• Confusing pipelines with atomic execution