Introduction to Redis Transactions: Conceptual Implementation with Lettuce

Welcome back! In the previous lesson, we explored Redis Pipelines, which optimize command execution by batching multiple commands. Today, we’ll focus on Redis Transactions, a powerful feature that queues a group of commands for execution in a single, sequential operation.

By the end of this lesson, you will understand how to implement transactions in Redis using a conceptual approach.

Redis Transactions allow you to queue multiple commands and then execute them sequentially once you commit (using EXEC). This is often described as an atomic operation, but it’s important to note:

• Atomic Execution: Commands within a transaction are sent to Redis as a block.
• (Partial) All or Nothing: If a command fails at queue time (e.g., invalid command), the entire transaction is discarded. However, if a command fails at runtime (e.g., a type error), Redis will still execute the other commands. For example, if you queue syncCommands.set("key1", "value1") and syncCommands.incr("key1") in a transaction, and incr() fails at runtime due to key1 being non-numeric, the set() command will still execute. This demonstrates that atomicity in Redis transactions applies only to queuing, not to execution.
• Isolation: Transactions prevent other clients from executing commands on the keys being modified until the transaction completes.
• Queuing of Commands: Commands are queued after a transaction is initiated with MULTI and only execute on EXEC.

In short, Redis discards the entire transaction if a command cannot be queued correctly, but does not roll back commands if a runtime error occurs after the transaction is committed.

Here’s how to conceptually implement a basic transaction using Redis with Lettuce:

1. Start a Transaction: Initiate a Redis transaction context that allows you to queue commands.

2. Queue Commands: Add the necessary Redis commands to the queue. For instance, you might want to set a key-value pair or increment a counter.

3. Commit the Transaction: Execute all queued commands in a single operation. The server commits these commands and executes them atomically.

4. Handle Results: Process the results returned by the server, indicating the success or failure of each command.

Example:

import io.lettuce.core.RedisClient;
import io.lettuce.core.api.StatefulRedisConnection;
import io.lettuce.core.api.sync.RedisCommands;
import io.lettuce.core.TransactionResult;

public class Main {

    public static void main(String[] args) {
        // Create a RedisClient with the appropriate URI
        RedisClient redisClient = RedisClient.create("redis://localhost:6379");

        // Open a connection
        StatefulRedisConnection<String, String> connection = redisClient.connect();
            
        // Obtain synchronous commands
        RedisCommands<String, String> syncCommands = connection.sync();
            
        // Start a transaction
        syncCommands.multi();
            
        // Queue commands
        syncCommands.set("key1", "value1");
        syncCommands.incr("counter");
                
        // Commit the transaction
        TransactionResult transactionResult = syncCommands.exec();
                
        // Print the transaction results
        transactionResult.forEach(result -> System.out.println("Result: " + result));
    }
}