Tipe data apa sing didukung Redis?

Question

Accepted Answer

Redis mendukung sawetara **struktur data** minangka nilai — strings, lists, hashes, sets, sorted sets, lan tipe-tipe khusus (streams, bitmaps, HyperLogLog, geospatial). Milih tipe sing tepat kanggo saben use case iku kunci kanggo nggunakake Redis kanthi efektif.

## Core data types

```bash
# STRING — the simplest (text, numbers, even binary up to 512MB)
SET key "value"
INCR counter            # atomic increment (strings can be counters)

# LIST — ordered list of strings (a linked list — fast push/pop at ends)
LPUSH mylist "a"        # push left
RPUSH mylist "b"        # push right
LRANGE mylist 0 -1      # get all → useful for queues, recent-items

# HASH — a map of field→value (like an object/record)
HSET user:1 name "Ann" age 30
HGET user:1 name        # => "Ann"  → great for storing objects

# SET — unordered unique strings
SADD tags "redis" "cache"
SISMEMBER tags "redis"  # membership test; SINTER/SUNION for set operations

# SORTED SET (ZSET) — unique members each with a SCORE, kept ordered by score
ZADD leaderboard 100 "Ann" 90 "Bob"
ZRANGE leaderboard 0 -1 WITHSCORES   # ranked → leaderboards, priority queues
```

## Specialized types

```text
STREAM      → an append-only log (like a message queue/event log with consumer groups)
BITMAP      → bit operations on strings (compact flags, e.g. daily active users)
HYPERLOGLOG → approximate unique counts using tiny memory (cardinality estimation)
GEOSPATIAL  → store/query locations (geo radius queries)
```

## Choosing the right type

```text
String      → simple values, counters, cached serialized data
List        → queues, stacks, recent-items, activity feeds
Hash        → objects/records (store fields of an entity together)
Set         → unique collections, membership tests, tags, relationships
Sorted Set  → leaderboards, rankings, priority queues, time-ordered data
→ Picking the right structure makes operations efficient and natural.
```

## Mengapa penting

Ngerteni tipe data Redis iku fundamental kanggo nggunakake Redis kanthi efektif, amarga kekuwatan Redis muncul tepaté saka **struktur data sing sugih** (ora mung penyimpanan key-value sederhana), mula ngerti lan kapan nggunakake saben tipe iku ilmu praktis sing wajib.

**Tipe-tipe inti** saben-saben cocog kanggo kabutuhan beda: **strings** (nilai sederhana lan atomic counters), **lists** (koleksi terurut kanggo queues, stacks, lan feeds item anyar), **hashes** (nyimpen obyek/record karo pirang-pirang field bareng — efisien kanggo entitas), **sets** (koleksi unik kanggo tes membership, tags, lan relationships, karo operasi set kayata intersection), lan **sorted sets** (anggota diperingkat miturut score — cocog alami kanggo leaderboards, rankings, lan priority queues).

Ngerteni **tipe-tipe khusus** — streams (append-only logs karo consumer groups, kanggo message queues lan event sourcing), bitmaps (flags kompak), HyperLogLog (unique counts perkiraan nang memori cilik), lan geospatial (location queries) — ngeperang apa sing Redis bisa lakoni kanthi efisien.

Paling penting, **milih tipe sing tepat** kanggo saben use case (sorted set kanggo leaderboard, hash kanggo obyek, list kanggo queue) iku apa sing nggawe operasi Redis efisien lan alami — nggunakake struktur salah nyebabake solusi kaya-kaya lan alon.

Karena nilai Redis muncul saka struktur datane lan nggunakake kanthi layak iku skill inti kanggo makarya karo Redis, lan amarga pilihan struktur langsung nentokake apa operasi efisien lan kode bersih, ngerteni tipe data Redis — tipe-tipe inti lan khusus lan kapan nggunakake saben — iku ilmu wajib sing sering ditrapake kanggo sapa wae sing nggunakake Redis, fondasi kanggo ndayani Redis kanthi efektif saliyane penyimpanan key-value trivial.