Integrasi Layanan Mikro Berbasis Peristiwa
Rancang dan terapkan pola komunikasi asinkron antar layanan mikro menggunakan Kafka.
Integrasi Layanan Mikro Berbasis Peristiwa adalah pelajaran Spring Boot 4 Microservices & REST APIs gratis di CoddyKit. Ini adalah pelajaran 3 dari 3. 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 Spring Boot 4 Microservices & REST APIs, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Spring Boot 4 Microservices & REST APIs mencakup 3 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
Event-Driven Microservices
Welcome to Event-Driven Microservice Integration! In this lesson, we'll learn how microservices can communicate asynchronously using events.
An event-driven architecture (EDA) is a software design pattern where services communicate by producing and consuming "events." These events are records of something that happened.
This approach helps create highly decoupled, scalable, and resilient systems.
Benefits of Asynchronous
Why choose event-driven communication over direct API calls (synchronous)?
- Decoupling: Services don't need to know about each other's existence. They only care about events.
- Resilience: If a consuming service is down, the events are stored and processed later, preventing cascading failures.
- Scalability: Producers can publish events without waiting for consumers, and multiple consumers can process events in parallel.
Kafka as Event Bus
Apache Kafka acts as a central "event bus" or message broker in many event-driven architectures.
Producers send events to Kafka topics, and consumers read events from these topics. Kafka stores these events durably, ensuring no data loss.
This allows services to communicate without direct connections, simplifying their design and deployment.
An OrderCreated Event
An event is a lightweight message indicating that something significant has occurred. It typically includes the event type, a timestamp, and relevant data.
Let's define a simple OrderCreatedEvent that our OrderService might publish when a new order is placed.
public class OrderCreatedEvent {
private String orderId;
private String customerId;
private double amount;
private long timestamp;
public OrderCreatedEvent(String orderId, String customerId, double amount) {
this.orderId = orderId;
this.customerId = customerId;
this.amount = amount;
this.timestamp = System.currentTimeMillis();
}
public String getOrderId() { return orderId; }
public String getCustomerId() { return customerId; }
public double getAmount() { return amount; }
public long getTimestamp() { return timestamp; }
@Override
public String toString() {
return "OrderCreatedEvent{" +
"orderId='" + orderId + '\'' +
", customerId='" + customerId + '\'' +
", amount=" + amount +
", timestamp=" + timestamp +
'}';
}
}Order Service as Producer
Our OrderService is responsible for creating new orders. Once an order is successfully created, it publishes an OrderCreatedEvent to a Kafka topic.
This event can then be consumed by other services, like an InventoryService, without the OrderService needing to know anything about them.
// Simulates a Kafka producer component
public class OrderProducer {
public void sendOrderCreatedEvent(OrderCreatedEvent event) {
// In a real Spring Boot app, this would use KafkaTemplate.send()
System.out.println("Producer: Sending event to Kafka topic 'orders':");
System.out.println(" " + event.toString());
}
}Try the Producer
Here's how you'd typically trigger the producer logic. Run this code to see the simulated event being "sent."
// Represents an event when an order is created
class OrderCreatedEvent {
private String orderId;
private String customerId;
private double amount;
private long timestamp;
public OrderCreatedEvent(String orderId, String customerId, double amount) {
this.orderId = orderId;
this.customerId = customerId;
this.amount = amount;
this.timestamp = System.currentTimeMillis();
}
public String getOrderId() { return orderId; }
public String getCustomerId() { return customerId; }
public double getAmount() { return amount; }
public long getTimestamp() { return timestamp; }
@Override
public String toString() {
return "OrderCreatedEvent{" +
"orderId='" + orderId + '\'' +
", customerId='" + customerId + '\'' +
", amount=" + amount +
", timestamp=" + timestamp +
'}';
}
}
// Simulates a Kafka producer component
class OrderProducer {
public void sendOrderCreatedEvent(OrderCreatedEvent event) {
System.out.println("Producer: Sending event to Kafka topic 'orders':");
System.out.println(" " + event.toString());
}
}
public class Main {
public static void main(String[] args) {
System.out.println("Order Service simulation started.");
OrderProducer producer = new OrderProducer();
// Simulate an order creation
OrderCreatedEvent event = new OrderCreatedEvent("ORD-001", "CUST-123", 99.99);
producer.sendOrderCreatedEvent(event);
System.out.println("Order Service simulation finished.");
}
}Inventory Service as Consumer
Our InventoryService needs to know when new orders are placed so it can update stock levels. It listens for OrderCreatedEvents from the Kafka topic.
When an event arrives, the consumer processes it, perhaps by deducting items from inventory or initiating a fulfillment process.
// Simulates a Kafka consumer component
public class InventoryConsumer {
public void listenOrderCreatedEvent(OrderCreatedEvent event) {
// In a real Spring Boot app, this would be an @KafkaListener method
System.out.println("Consumer: Received event from Kafka topic 'orders':");
System.out.println(" " + event.toString());
System.out.println(" Updating inventory for order " + event.getOrderId());
}
}Try the Consumer
This code simulates the InventoryConsumer listening for an event. In a real scenario, this would run continuously, processing incoming events.
// Represents an event when an order is created
class OrderCreatedEvent {
private String orderId;
private String customerId;
private double amount;
private long timestamp;
public OrderCreatedEvent(String orderId, String customerId, double amount) {
this.orderId = orderId;
this.customerId = customerId;
this.amount = amount;
this.timestamp = System.currentTimeMillis();
}
public String getOrderId() { return orderId; }
public String getCustomerId() { return customerId; }
public double getAmount() { return amount; }
public long getTimestamp() { return timestamp; }
@Override
public String toString() {
return "OrderCreatedEvent{" +
"orderId='" + orderId + '\'' +
", customerId='" + customerId + '\'' +
", amount=" + amount +
", timestamp=" + timestamp +
'}';
}
}
// Simulates a Kafka consumer component
class InventoryConsumer {
public void listenOrderCreatedEvent(OrderCreatedEvent event) {
System.out.println("Consumer: Received event from Kafka topic 'orders':");
System.out.println(" " + event.toString());
System.out.println(" Updating inventory for order " + event.getOrderId());
}
}
public class Main {
public static void main(String[] args) {
System.out.println("Inventory Service simulation started.");
InventoryConsumer consumer = new InventoryConsumer();
// Simulate receiving an event (e.g., from Kafka)
// This event would typically come from a Producer
OrderCreatedEvent receivedEvent = new OrderCreatedEvent("ORD-001", "CUST-123", 99.99);
consumer.listenOrderCreatedEvent(receivedEvent);
System.out.println("Inventory Service simulation finished.");
}
}Key Considerations
When working with event-driven systems, two key concepts are important:
- Eventual Consistency: Data across different services might not be instantly consistent. It will become consistent "eventually."
- Idempotency: Consumers should be designed to handle duplicate events gracefully. Processing the same event multiple times should not change the outcome.
These are crucial for building robust asynchronous microservices.
Integration Check
Which of the following are key benefits of using an event-driven architecture for microservice integration compared to direct synchronous API calls?
Event-Driven Recap
Great job! In this lesson, you've learned about event-driven microservice integration:
- The benefits of asynchronous communication like decoupling, resilience, and scalability.
- How Kafka serves as an event bus.
- The roles of producer and consumer microservices in publishing and processing events.
- Important concepts like eventual consistency and idempotency.
You're now ready to design more robust and scalable microservice interactions!
Belajar Java 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
- 24
- Pelajaran
- 93
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Integrasi Layanan Mikro Berbasis Peristiwa” gratis?
Ya — teks lengkap “Integrasi Layanan Mikro Berbasis Peristiwa” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Spring Boot 4 Microservices & REST APIs, upgrade ke CoddyKit PRO. Kursus Spring Boot 4 Microservices & REST APIs mencakup 3 pelajaran total.
Apa yang akan aku pelajari di “Integrasi Layanan Mikro Berbasis Peristiwa”?
Rancang dan terapkan pola komunikasi asinkron antar layanan mikro menggunakan Kafka. Kamu berlatih Spring Boot 4 Microservices & REST APIs 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 Spring Boot 4 Microservices & REST APIs?
Tidak diperlukan pengalaman sebelumnya. Spring Boot 4 Microservices & REST APIs 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 3 dari 3.
Berapa lama pelajaran “Integrasi Layanan Mikro Berbasis Peristiwa” 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 Spring Boot 4 Microservices & REST APIs ini?
Ya. Setiap pelajaran Spring Boot 4 Microservices & REST APIs 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
- Pengantar Produsen Kafka
- Membangun Konsumen Kafka
- Integrasi Layanan Mikro Berbasis Peristiwa