0Pricing
Redis Caching & Messaging (Pub/Sub, Streams) · Pelajaran

Struktur Data dan Perintah Stream

Pelajari cara menambahkan entri (`XADD`), membaca dari stream (`XREAD`), dan mengelola panjang stream.

Struktur Data dan Perintah Stream adalah pelajaran Redis Caching & Messaging (Pub/Sub, Streams) gratis di CoddyKit. Ini adalah pelajaran 2 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Redis Caching & Messaging (Pub/Sub, Streams), dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Redis Caching & Messaging (Pub/Sub, Streams) mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

Welcome to Stream Data

In the previous lesson, we learned what Redis Streams are. Now, let's dive into their core structure and how we interact with them.

Redis Streams are powerful, append-only data structures that act like a log, storing a sequence of entries. Each entry has a unique ID and a set of field-value pairs.

Stream Entry Anatomy

Each entry in a Redis Stream is like a small record. It consists of:

  • Entry ID: A unique identifier, typically a timestamp and a sequence number (e.g., 1678886400000-0).
  • Field-Value Pairs: One or more key-value pairs representing the actual data of the entry (e.g., sensor-id: 123, temperature: 25.5).

Think of it like a mini-hash map stored chronologically within the stream.

Adding Entries with XADD

To add a new entry to a Redis Stream, we use the XADD command. This command appends a new entry to the end of the stream, generating a unique ID.

The basic syntax is:

XADD key ID field value [field value ...]

For the ID argument, you'll typically use * to let Redis automatically assign a unique ID based on the current time.

XADD Command Example

Let's add some sensor data to a stream named sensor_readings. We'll use * to let Redis automatically assign a unique ID.

XADD sensor_readings * sensor-id 101 temperature 23.5 humidity 60
XADD sensor_readings * sensor-id 102 temperature 24.1 humidity 62

Reading from Streams: XREAD

Once data is in a stream, you'll want to read it. The XREAD command is used for this purpose. It allows you to read entries from one or more streams, starting from a specific ID.

A common way to read from the very beginning of a stream is to use 0-0 as the starting ID for that stream.

Basic XREAD Operations

Let's read the entries we just added. We can specify COUNT to limit the number of entries returned. The $ ID means 'read only new entries added since the last time I read' or 'from now' if it's the first read. It's great for tailing a stream!

XREAD COUNT 2 STREAMS sensor_readings 0-0
XREAD STREAMS sensor_readings $

Managing Stream Length: MAXLEN

Streams can grow infinitely, consuming a lot of memory. To prevent this, Redis allows you to limit the maximum length of a stream using the MAXLEN option with XADD.

When the stream exceeds the specified length, older entries are automatically evicted from the head of the stream.

XADD with MAXLEN Example

We can add entries and ensure our sensor_readings stream never exceeds a certain number of entries. Using ~ before the count makes the trimming approximate, which is faster and often sufficient.

XADD sensor_readings MAXLEN ~ 3 * sensor-id 103 temperature 24.8 humidity 61
XADD sensor_readings MAXLEN ~ 3 * sensor-id 104 temperature 25.2 humidity 63
XADD sensor_readings MAXLEN ~ 3 * sensor-id 105 temperature 25.0 humidity 60
XLEN sensor_readings

Quick Check: Stream Commands

You've learned about adding and reading stream entries, as well as managing stream length. Let's test your understanding.

Recap: Stream Basics

Great job! In this lesson, you mastered the fundamental commands for interacting with Redis Streams:

  • XADD: To append new entries with unique IDs and field-value pairs.
  • XREAD: To retrieve entries from streams, starting from a specific ID or reading new entries with $.
  • MAXLEN: To control stream size during XADD operations, preventing unbounded memory growth.

Next, we'll explore how Streams provide message persistence and ordered delivery, differentiating them from Pub/Sub.

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Struktur Data dan Perintah Stream” gratis?

Ya — teks lengkap “Struktur Data dan Perintah Stream” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Redis Caching & Messaging (Pub/Sub, Streams), upgrade ke CoddyKit PRO. Kursus Redis Caching & Messaging (Pub/Sub, Streams) mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Struktur Data dan Perintah Stream”?

Pelajari cara menambahkan entri (`XADD`), membaca dari stream (`XREAD`), dan mengelola panjang stream. Kamu berlatih Redis Caching & Messaging (Pub/Sub, Streams) dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Redis Caching & Messaging (Pub/Sub, Streams)?

Tidak diperlukan pengalaman sebelumnya. Redis Caching & Messaging (Pub/Sub, Streams) di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 4.

Berapa lama pelajaran “Struktur Data dan Perintah Stream” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Redis Caching & Messaging (Pub/Sub, Streams) ini?

Ya. Setiap pelajaran Redis Caching & Messaging (Pub/Sub, Streams) menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

  1. Apa Itu Redis Streams?
  2. Struktur Data dan Perintah Stream
  3. Persistensi Pesan Stream
  4. Membatasi dan Memangkas Stream
← Kembali ke Redis Caching & Messaging (Pub/Sub, Streams)