Mastering Redis: Installation, Data Types, and Advanced Features Explained

Installation

Download the desired Redis source package (e.g., redis-4.0.1.tar.gz) from the official Redis website.

Extract the archive: tar -zxvf redis-4.0.1.tar.gz Enter the extracted directory and compile: make Start the server: ./redis-server. The server logs indicate a successful start.

Open a client: ./redis-cli and run INFO to view runtime statistics.

Data Types

Redis provides five core data structures, each with dedicated commands and an internal representation based on redisObject.

String : Binary‑safe byte sequence (max 512 MiB). Commands: SET, GET, INCR, DECR, MGET. Stored as raw string or integer in redisObject.encoding.

Hash : Mapping of field‑value pairs, useful for representing objects. Commands: HSET, HGET, HGETALL. Internally a hash table referenced by a redisObject.

List : Ordered collection of strings, allowing duplicates. Commands: LPUSH, RPUSH, LPOP, RPOP, LRANGE. Implemented as a doubly‑linked list.

Set : Unordered collection of unique strings. Commands: SADD, SPOP, SMEMBERS, SUNION. Implemented with a hash table where values are NULL, giving O(1) membership checks.

Sorted Set (Zset) : Set of strings each associated with a numeric score for ordering. Commands: ZADD, ZRANGE, ZREM, ZCARD. Uses a hash map for O(1) look‑up and a skip‑list for ordered traversal.

Advanced Features

Publish/Subscribe : Decouples producers and consumers. Publishers send messages with PUBLISH; subscribers receive them via SUBSCRIBE or PSUBSCRIBE. Supports many‑to‑many delivery.

Transactions : Enclose commands between MULTI and EXEC. Commands are queued and executed atomically, preventing interleaving from other clients.

Pipelining : Clients can send a batch of commands without waiting for individual replies, then read all responses at once, reducing round‑trip latency.

Persistence : Two mechanisms—RDB snapshots and AOF (Append‑Only File). RDB creates point‑in‑time snapshots; AOF logs every write operation for replay during recovery. Both are enabled via the redis.conf file.

Java Client Example

The popular Java client library is Jedis . Repository: https://github.com/xetorthio/jedis

Maven dependency:

<dependency>
  <groupId>redis.clients</groupId>
  <artifactId>jedis</artifactId>
  <version>3.7.1</version>
</dependency>

Typical unit test for hash operations:

try (Jedis jedis = new Jedis("localhost", 6379)) {
    jedis.hset("car:1", "brand", "Toyota");
    jedis.hset("car:1", "color", "red");
    String brand = jedis.hget("car:1", "brand");
    assertEquals("Toyota", brand);
}

Performance Highlights

Throughput: ~110,000 SET and ~81,000 GET operations per second on a single core.

All operations are atomic because Redis runs a single‑threaded event loop.

Rich data‑type support enables use cases such as caching, session storage, counters, and message queues.