Redis inaweza kutekeleza Lua scripts upande wa server — kuendesha amri nyingi kama operesheni moja atomiki. Scripts huwezesha mantiki atomiki changamano, kupunguza network round-trips, na ndio njia inayopendekezwa kufanya operesheni atomiki nyingi katika Redis.
# EVAL runs a Lua script; KEYS[] and ARGV[] pass keys and arguments
EVAL 1 mykey myvalue
EVAL 1 lock:resource mytoken
Scripts hutumia redis.call() kuendesha amri, na KEYS[] (jina la funguo) na ARGV[] (hoja) zinachorwa ndani. Script nzima inaendesha atomiki kama kitengo kimoja.
✓ ATOMICITY — the ENTIRE script runs as one unit, no other commands interleave
→ perfect for read-modify-write logic that must be atomic (locks, conditional updates,
rate limiting, complex counters) — better than MULTI/EXEC for conditional logic
✓ FEWER ROUND-TRIPS — multiple operations in ONE call to Redis (less network latency)
✓ Custom LOGIC server-side — conditionals, loops, computations near the data
# load a script once, then call by its SHA hash (avoids resending the script each time)
SCRIPT LOAD "return redis.call('GET', KEYS[1])" # => returns a SHA1 hash
EVALSHA <sha> 1 mykey # run the cached script by hash
EVALSHA inaendesha script iliyoingizwa hapo awali kwa kutumia hash yake — inafaa kwa scripts zinazotumika mara kwa mara (script inacheshwa upande wa server).
⚠️ Scripts BLOCK the server while running (Redis is single-threaded) → keep them FAST
and simple (no slow loops/operations — they'd stall ALL clients)
⚠️ Scripts should be deterministic; pass keys via KEYS[] (for cluster correctness)
→ Use scripts for short, atomic logic — not heavy computation.
Kuelewa Lua scripting katika Redis ni ujuzi wa kiwango cha juu uliothamini kwa kutekeleza operesheni atomiki changamano, kwa hivyo ni muhimu kwa Redis ya juu.
Thamani ya msingi ni atomicity kwa mantiki multi-step: Lua script inaendesha kabisa kama kitengo kimoja atomiki (hakuna amri nyingine zinazoingia), na kwa hiyo ndio njia inayopendekezwa kufanya operesheni read-modify-write ambayo lazima iwe atomiki — kama updates yenye masharti, release yenye usalama wa lock (futa tu ikiwa token inalingana), rate limiting, na counters changamano — mara nyingi ni bora kuliko MULTI/EXEC kwa sababu scripts inasaidia conditional logic (transaction haiwezi kufanya maamuzi kulingana na reads za kati, lakini script inaweza).
Hii hutatua haja halisi kwa operesheni atomiki zaidi ya amri moja.
Faida ya pili ni network round-trips ndogo (operesheni nyingi kwa kupiga simu moja, kupunguza latency) na kuendesha custom logic upande wa server (karibu na data).
Kuelewa EVALSHA (kuchora scripts kwa hash ili kuzuia kusambaza tena) ni mbinu ya ufanisi wa vitendo kwa scripts zinazotumika mara kwa mara.
Kwa umuhimu, kuelewa onyo ni muhimu: scripts zuia server yenye thread moja wakati ikiwa ikiwa, kwa hivyo lazima iwe haraka na rahisi (script ya polepole inakamatia wakilishi wote — hatari halisi ya utendaji), na scripts lazima iwe ya kuamua kwa funguo kupita kwa KEYS[] (kwa usahihi wa cluster).
Ufahamu huu hudhibiti kumkosea scripts kwa hesabu nzito.
Kwa kuwa operesheni atomiki changamano ni haja halisi (locks, conditional logic, atomic multi-step updates), na kwa kuwa Lua scripts hutoa mantiki atomiki, single-round-trip, server-side ambayo ni njia inayopendekezwa kwa ajili yao (na onyo muhimu kuhusu kuzuia), kuelewa Lua scripting — jinsi inavyofanya kazi, kwa nini ni atomiki na muhimu, EVALSHA caching, na onyo la ubaki haraka — ni ujuzi wa kiwango cha juu uliothamini kwa Redis ya juu, zana sahihi kwa mantiki multi-step atomiki na mada inayoonyesha ujuzi wa Redis wa kina.