Why EVALSHA for cached scripts in Redis? - Purpose & Use Cases

The Big Idea

What if you could speed up your Redis scripts by never sending the full code again?

The Scenario

Imagine you have a busy coffee shop where every order requires writing down the recipe from scratch each time. This slows down the baristas and causes mistakes.

The Problem

Writing the same script repeatedly is slow and error-prone. Each time you send the full script, it wastes time and bandwidth, and you risk typos or inconsistencies.

The Solution

EVALSHA lets you store the script once and then call it by its unique ID (hash). This means faster execution, less data sent, and fewer errors.

Before vs After

✗ Before

EVAL "return redis.call('GET', KEYS[1])" 1 mykey

✓ After

EVALSHA <sha1-hash> 1 mykey

What It Enables

You can run complex Redis scripts quickly and reliably by referencing cached versions instead of resending full scripts.

Real Life Example

A gaming app uses EVALSHA to quickly update player scores with a stored script, reducing lag and improving user experience.

Key Takeaways

Manually sending scripts wastes time and risks errors.

EVALSHA caches scripts by hash for fast, reliable calls.

This improves performance and reduces network load.