Command Execution

How does Redis handle a command from the moment it leaves your client to the moment a response is returned? Explore the atomic execution model and the command lifecycle.

Command Processor

Input Command

Network Receive

Redis receives the raw command over a TCP socket.

Command Parsing

The RESP (Redis Serialization Protocol) parser extracts the command and arguments.

Execution Plan

Redis finds the command implementation and validates arguments.

Atomic Execution

The command is executed in the single-threaded engine.

Response Write

The result is sent back to the client.

Real-time Memory Map

app:name

string

Internal Encoding

embstr

Value Content

"RedisVisualizer"

counter

string

Internal Encoding

int

Value Content

Execution Logs

No commands executed yet...

Atomicity

Commands in Redis are atomic. Once a command starts, no other command can run until it finishes. This guarantees data consistency without locks.

Fast Path

Most Redis commands prioritize O(1) or O(log N) time complexity. This ensures the single thread isn't blocked for long periods.

Latency Sources

High latency usually comes from networking, slow commands (like KEYS *), or disk I/O when persistence is enabled.

The RESP Protocol

Redis uses a simple request-response protocol called RESP. It's human-readable and easy to parse.

# Array of 3 elements

# String of 3 bytes

SET

user

$10

Antigravity

This format allows Redis to know exactly how many bytes to read from the network before starting to parse, making it extremely efficient.