Redis Mastery: Practical Tips, Data Structures, and Best‑Practice Guidelines

Key Features

SET command enhancements : Since Redis 2.6.12 the SET command accepts expiration flags ( EX / PX) and conditional flags ( NX / XX), removing the need for a separate EXPIRE call.

Bitmap : Efficient for massive binary flags (e.g., user state tracking) and serves as the basis for Bloom filters. Example implementation: https://github.com/Baqend/Orestes-Bloomfilter

Streams : Added in Redis 4, a lightweight Kafka‑like log that solves PUB/SUB reliability and blocked‑list consumption issues. Intro: https://redis.io/topics/streams-intro

Usage Recommendations

Assign appropriate TTLs : Use expiration to prevent uncontrolled memory growth, especially when Redis is used as a cache.

Pipeline wisely : Group independent commands in a pipeline, but avoid pipelining when later commands depend on earlier results. Consider failure handling for atomicity.

Use namespaces : Prefix keys (e.g., u:${id}) to simplify management, enable shard parameters, and improve statistics.

Choose the right data structure : Know each structure’s purpose; for example SCARD returns a set’s size without fetching all elements. Avoid storing large objects in Sets/Hashes because Redis is single‑threaded and large objects increase network I/O and memory fragmentation. For very large blobs consider alternatives such as Memcached.

Disable risky commands : Rename or disable commands via the rename-command configuration directive.

Leverage Lua scripts : Use Lua for atomic multi‑key operations, but keep scripts short and simple to avoid CPU spikes in high‑QPS scenarios.

Dynamic configuration : CONFIG SET can modify parameters like maxmemory without restart; view mutable settings with CONFIG GET *.

Best Practices

Key naming : Use clear, readable names to aid debugging and analytics.

Key length : Keep names concise when millions of keys are expected; long prefixes waste memory.

Avoid overusing Lua : Excessive scripting in high‑traffic services can saturate Redis’s single thread.

Monitor memory and performance

Run INFO MEMORY to inspect usage, fragmentation, and allocation.

Use SLOWLOG GET N to identify slow commands.

Sample large keys with redis-cli --bigkeys (see https://redis.io/topics/rediscli).

Understanding Redis beyond basic commands—its data structures, configuration knobs, and operational metrics—enables developers to harness its full potential while avoiding common pitfalls such as memory bloat or performance degradation.