Redis Overview: Architecture, Persistence, High Availability, and Client Features

Redis is an open‑source, in‑memory data store that can serve as a database, cache, and message broker, supporting data types such as strings, lists, hashes, sets, sorted sets, bitmaps, hyperloglogs, and geospatial indexes.

Typical usage starts with simple HTTP cache‑control, then moves to in‑process memory caching, and finally adopts a dedicated Redis server when memory pressure on API servers becomes a bottleneck.

Server‑side features include persistence (RDB/AOF) to prevent data loss, high‑availability mechanisms like Sentinel for monitoring and automatic failover, replication for creating standby copies, and Redis Cluster which shards data across multiple nodes using hash slots.

On the client side, Redis offers rich data structures, atomic transactions, Lua scripting for complex server‑side logic, pipelining to reduce round‑trip latency, and a distributed lock implementation (Redlock) using SET NX PX combined with Lua verification.

SET resource_name my_random_value NX PX 30000
if redis.call("get",KEYS[1]) == ARGV[1] then
    return redis.call("del",KEYS[1])
else
    return 0
end

The article concludes that understanding these abstract capabilities helps select appropriate Redis features for specific scenarios rather than focusing solely on low‑level implementation details.