Sumber Peristiwa dengan Kafka
Terapkan arsitektur sumber peristiwa menggunakan Kafka untuk membangun sistem yang tangguh dan dapat diaudit.
Sumber Peristiwa dengan Kafka adalah pelajaran Apache Kafka & Stream Processing Fundamentals gratis di CoddyKit. Ini adalah pelajaran 1 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.
What is Event Sourcing?
Event Sourcing is an architectural pattern where all changes to application state are stored as a sequence of immutable events.
Instead of just storing the current state of an entity, you store every single action that led to that state. Think of it like a ledger in accounting.
This means your database doesn't just hold the 'current version' of data, but a complete, ordered history of every change.
Why Use Event Sourcing?
Event Sourcing offers several compelling benefits for modern applications:
- Full Audit Trail: You get a complete, unalterable history of everything that happened.
- Debugging & Analysis: Easily replay events to understand issues or analyze past behavior.
- Temporal Queries: Reconstruct state at any point in time.
- Resilience: If a read model fails, you can rebuild it by replaying events.
Core Event Sourcing Concepts
Let's define the main components:
- Events: Immutable facts describing something that has happened in the past (e.g.,
OrderPlaced,ItemAdded). - Event Store: A database that stores these events chronologically. It's the single source of truth.
- State Reconstruction: The process of reading and applying events from the store to build an entity's current state or a read-optimized view.
Kafka as the Event Store
Apache Kafka is an excellent choice for an event store due to its core features:
- Distributed Log: Kafka topics are essentially durable, ordered, and immutable logs of events.
- High Throughput: It can handle massive volumes of events efficiently.
- Durability: Events are replicated across brokers, ensuring fault tolerance.
- Scalability: Easily scales to accommodate growing event streams.
Kafka provides the perfect backbone for storing and distributing events in an event-sourced system.
Designing Your Events
Events are the heart of event sourcing. Good event design is crucial:
- Immutability: Once an event is created, it should never change.
- Fact-based: Describe a past occurrence, not a command or future action.
- Rich Data: Include all necessary data for future interpretation, as you can't easily query the 'current state'.
- Past Tense Naming: Use names like
UserCreated,ProductPriceUpdated.
Events should be self-contained and easily serializable (e.g., JSON, Avro).
Producing Events to Kafka
Here's how you might send a simple UserCreated event to a Kafka topic named user_events. This event represents a fact that a user was created.
Try running this example:
import org.apache.kafka.clients.producer.*;
import org.apache.kafka.common.serialization.StringSerializer;
import java.util.Properties;
public class EventProducer {
public static void main(String[] args) {
Properties props = new Properties();
props.put("bootstrap.servers", "localhost:9092");
props.put("key.serializer", StringSerializer.class.getName());
props.put("value.serializer", StringSerializer.class.getName());
try (Producer<String, String> producer = new KafkaProducer<>(props)) {
String topic = "user_events";
String key = "user-123";
String value = "{\"type\":\"UserCreated\",\"id\":\"user-123\"}";
ProducerRecord<String, String> record = new ProducerRecord<>(topic, key, value);
producer.send(record).get();
System.out.println("Event sent: " + value);
} catch (Exception e) {
e.printStackTrace();
}
}
}Consuming Events for State
Consumers read events from Kafka topics to build or update their read models (projections) or reconstruct the current state of an entity. They apply events in order.
This example shows a consumer listening for events on the user_events topic:
import org.apache.kafka.clients.consumer.*;
import org.apache.kafka.common.serialization.StringDeserializer;
import java.time.Duration;
import java.util.Collections;
import java.util.Properties;
public class EventConsumer {
public static void main(String[] args) {
Properties props = new Properties();
props.put("bootstrap.servers", "localhost:9092");
props.put("group.id", "event_sourcing_group");
props.put("key.deserializer", StringDeserializer.class.getName());
props.put("value.deserializer", StringDeserializer.class.getName());
props.put("auto.offset.reset", "earliest");
try (Consumer<String, String> consumer = new KafkaConsumer<>(props)) {
consumer.subscribe(Collections.singletonList("user_events"));
System.out.println("Polling for events...");
ConsumerRecords<String, String> records = consumer.poll(Duration.ofSeconds(5));
for (ConsumerRecord<String, String> record : records) {
System.out.println("Processed event: " + record.value());
}
consumer.commitSync();
} catch (Exception e) {
e.printStackTrace();
}
}
}Advantages with Kafka ES
Combining Event Sourcing with Kafka brings powerful advantages:
- Decoupling: Producers and consumers are independent, communicating only via events.
- Event Replay: Easily rebuild or create new read models by replaying historical events.
- Real-time Analytics: Leverage Kafka Streams or KSQL to process events in real-time for immediate insights.
- Scalability: Handle high data volumes and numerous consumers without impacting performance.
Challenges & Considerations
While powerful, Event Sourcing with Kafka also has challenges:
- Event Versioning: How do you handle changes to event structures over time? Migration strategies are needed.
- Eventual Consistency: Read models are built asynchronously, so queries might reflect a slightly older state.
- Complexity: Can be more complex than traditional CRUD for simple applications.
- Data Privacy: Deleting data (e.g., GDPR) requires careful design, as events are immutable.
Quick Check: Event Sourcing
Which of the following is a key characteristic of an event in Event Sourcing?
Recap: Event Sourcing with Kafka
In this lesson, you've learned about Event Sourcing, an architecture where all state changes are stored as an ordered sequence of immutable events.
Kafka acts as an ideal, scalable, and durable event store, enabling you to build resilient and auditable systems. We explored how to design events and saw simple Java examples for producing and consuming them.
Understanding these patterns is crucial for building robust, real-time data platforms.
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Sumber Peristiwa dengan Kafka” gratis?
Ya — teks lengkap “Sumber Peristiwa dengan Kafka” 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 “Sumber Peristiwa dengan Kafka”?
Terapkan arsitektur sumber peristiwa menggunakan Kafka untuk membangun sistem yang tangguh dan dapat diaudit. 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 1 dari 4.
Berapa lama pelajaran “Sumber Peristiwa dengan Kafka” 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
- Sumber Peristiwa dengan Kafka
- Pengambilan Data Perubahan (CDC)
- Pola Komunikasi Layanan Mikro
- Pola Outbox untuk Publikasi Peristiwa yang Andal