Konsep KStream & KTable
Bedakan KStream (aliran catatan per catatan) dan KTable (aliran log perubahan yang merepresentasikan tampilan terwujud) dalam Kafka Streams.
Konsep KStream & KTable adalah pelajaran Apache Kafka & Stream Processing Fundamentals 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 Apache Kafka & Stream Processing Fundamentals, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Apache Kafka & Stream Processing Fundamentals mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
KStream & KTable Unveiled
In Kafka Streams, KStream and KTable are fundamental data abstractions. They represent different ways to view and process your data.
Understanding their differences is key to building powerful, real-time stream processing applications.
KStream: A Stream of Events
A KStream represents an unbounded, immutable sequence of data records. Think of it like a traditional log or event stream.
- Each record is treated as a distinct, independent event.
- Records are processed one by one, in the order they arrive.
- It never "updates" a previous record; new records are always additions.
It's perfect for handling events like clicks, sensor readings, or financial transactions.
KStream in Action: Filtering
Here's a simple Kafka Streams application that uses a KStream to filter messages. It processes each record individually.
This example will filter a stream of text messages, keeping only those that contain the word "event".
import org.apache.kafka.common.serialization.Serdes;
import org.apache.kafka.streams.KafkaStreams;
import org.apache.kafka.streams.StreamsBuilder;
import org.apache.kafka.streams.StreamsConfig;
import org.apache.kafka.streams.kstream.KStream;
import java.util.Properties;
public class KStreamFilter {
public static void main(String[] args) {
Properties props = new Properties();
props.put(StreamsConfig.APPLICATION_ID_CONFIG, "kstream-filter-app");
props.put(StreamsConfig.BOOTSTRAP_SERVERS_CONFIG, "localhost:9092");
props.put(StreamsConfig.DEFAULT_KEY_SERDE_CLASS_BY_KEY_CLASS_CONFIG, Serdes.String().getClass());
props.put(StreamsConfig.DEFAULT_VALUE_SERDE_CLASS_BY_KEY_CLASS_CONFIG, Serdes.String().getClass());
StreamsBuilder builder = new StreamsBuilder();
KStream<String, String> sourceStream = builder.stream("input-topic");
KStream<String, String> filteredStream = sourceStream
.filter((key, value) -> value.contains("event"));
filteredStream.to("output-topic");
KafkaStreams streams = new KafkaStreams(builder.build(), props);
System.out.println("KStream filter topology created.");
System.out.println("It filters messages containing 'event'.");
// In a real application, you would call streams.start();
// and manage its lifecycle, e.g., using a shutdown hook.
}
}KTable: A Dynamic View
A KTable represents a changelog stream, where each record signifies an update or deletion to a row in a table. It's like a database table that's constantly being updated.
- Each record's value is considered the "latest" value for its key.
- When a new record arrives with an existing key, it overwrites the previous value.
- Perfect for maintaining the current state of data.
Think of user profiles, stock prices, or current inventory levels.
KTable in Action: Latest State
This example demonstrates a KTable maintaining the latest value for each key. Imagine tracking the most recent status for various sensors.
When a new message arrives for a sensor, its status in the KTable is updated to the new value.
import org.apache.kafka.common.serialization.Serdes;
import org.apache.kafka.streams.KafkaStreams;
import org.apache.kafka.streams.StreamsBuilder;
import org.apache.kafka.streams.StreamsConfig;
import org.apache.kafka.streams.kstream.KTable;
import org.apache.kafka.streams.kstream.Materialized;
import java.util.Properties;
public class KTableLatestState {
public static void main(String[] args) {
Properties props = new Properties();
props.put(StreamsConfig.APPLICATION_ID_CONFIG, "ktable-latest-state-app");
props.put(StreamsConfig.BOOTSTRAP_SERVERS_CONFIG, "localhost:9092");
props.put(StreamsConfig.DEFAULT_KEY_SERDE_CLASS_BY_KEY_CLASS_CONFIG, Serdes.String().getClass());
props.put(StreamsConfig.DEFAULT_VALUE_SERDE_CLASS_BY_KEY_CLASS_CONFIG, Serdes.String().getClass());
StreamsBuilder builder = new StreamsBuilder();
KTable<String, String> latestStatusTable = builder
.table("sensor-updates", Materialized.as("latest-sensor-status"));
// The KTable is defined. In a real app, you might print
// its contents to another topic or join it with a KStream.
// latestStatusTable.toStream().to("latest-status-output-topic");
KafkaStreams streams = new KafkaStreams(builder.build(), props);
System.out.println("KTable latest state topology created.");
System.out.println("It tracks the most recent status for each sensor.");
}
}KStream vs. KTable: Key Differences
While both process data, their fundamental nature differs significantly:
- KStream: Each record is an event. It's a sequence of facts. "Something happened."
- KTable: Each record is an update. It represents the current state. "This is the current value."
Think of KStream as a transaction log and KTable as the current balance sheet.
When to Use KStream
KStreams are ideal when you need to react to individual events or process data without maintaining a long-term state based on keys.
- Event logging: Storing every user action.
- Real-time alerts: Notifying immediately when a specific event occurs.
- Data enrichment (stateless): Adding information to each event based on its content.
- Filtering and mapping: Transforming events one by one.
When to Use KTable
KTables are perfect for applications that need to maintain and query the latest state of data, often for aggregations or joins.
- Current inventory: Tracking stock levels for products.
- User profiles: Storing the most recent profile details.
- Aggregations: Counting unique users, summing sales over time (when aggregated results are stored as a KTable).
- Joining streams with tables: Enriching a KStream with current KTable data.
From Stream to Table: Aggregation
You can transform a KStream into a KTable using stateful operations like aggregation. This converts a series of events into a continuously updated state.
For example, counting occurrences of words from a stream of sentences will result in a KTable where the key is the word and the value is its current count.
import org.apache.kafka.common.serialization.Serdes;
import org.apache.kafka.streams.KafkaStreams;
import org.apache.kafka.streams.StreamsBuilder;
import org.apache.kafka.streams.StreamsConfig;
import org.apache.kafka.streams.kstream.KStream;
import org.apache.kafka.streams.kstream.KTable;
import org.apache.kafka.streams.kstream.Materialized;
import org.apache.kafka.streams.kstream.Produced;
import java.util.Arrays;
import java.util.Properties;
public class KStreamToKTable {
public static void main(String[] args) {
Properties props = new Properties();
props.put(StreamsConfig.APPLICATION_ID_CONFIG, "word-count-app");
props.put(StreamsConfig.BOOTSTRAP_SERVERS_CONFIG, "localhost:9092");
props.put(StreamsConfig.DEFAULT_KEY_SERDE_CLASS_BY_KEY_CLASS_CONFIG, Serdes.String().getClass());
props.put(StreamsConfig.DEFAULT_VALUE_SERDE_CLASS_BY_KEY_CLASS_CONFIG, Serdes.String().getClass());
StreamsBuilder builder = new StreamsBuilder();
KStream<String, String> textLines = builder.stream("text-input");
KTable<String, Long> wordCounts = textLines
.flatMapValues(value -> Arrays.asList(value.toLowerCase().split("\\W+")))
.groupBy((key, word) -> word)
.count(Materialized.as("counts-store"));
wordCounts.toStream().to("word-counts-output", Produced.with(Serdes.String(), Serdes.Long()));
KafkaStreams streams = new KafkaStreams(builder.build(), props);
System.out.println("KStream to KTable topology created (Word Count).");
System.out.println("Counts words from 'text-input' and stores counts in a KTable.");
}
}KStream vs. KTable Quiz
Which of the following statements accurately describe a KTable?
KStream & KTable Recap
You've learned the core differences between KStream and KTable in Kafka Streams!
- KStream: An event stream, processing individual, immutable records.
- KTable: A changelog stream representing a materialized, updatable view of data.
Choosing the right abstraction is crucial for efficient and meaningful real-time data processing. Next, we'll explore stateless vs. stateful operations in Kafka Streams.
Belajar Apache Kafka & Stream Processing Fundamentals dengan tutor AI — gratis
Tulis dan jalankan kode asli di browser kamu, dapatkan bantuan instan dari tutor AI 24/7, dan lanjutkan di mana kamu tinggalkan di web atau aplikasi.
- Kursus
- 12
- Pelajaran
- 48
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Konsep KStream & KTable” gratis?
Ya — teks lengkap “Konsep KStream & KTable” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Apache Kafka & Stream Processing Fundamentals, upgrade ke CoddyKit PRO. Kursus Apache Kafka & Stream Processing Fundamentals mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Konsep KStream & KTable”?
Bedakan KStream (aliran catatan per catatan) dan KTable (aliran log perubahan yang merepresentasikan tampilan terwujud) dalam Kafka Streams. Kamu berlatih Apache Kafka & Stream Processing Fundamentals 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 Apache Kafka & Stream Processing Fundamentals?
Tidak diperlukan pengalaman sebelumnya. Apache Kafka & Stream Processing Fundamentals 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 “Konsep KStream & KTable” 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 Apache Kafka & Stream Processing Fundamentals ini?
Ya. Setiap pelajaran Apache Kafka & Stream Processing Fundamentals 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
- Membangun Aplikasi Kafka Streams Sederhana
- Konsep KStream & KTable
- Operasi Tanpa Status vs. Berstatus
- Serdes dan Serialisasi Data di Kafka Streams