0Pricing
Spring Boot 4 Microservices & REST APIs · Lektion

Ereignisgesteuerte Microservice-Integration

Entwerfen und implementieren Sie mithilfe von Kafka asynchrone Kommunikationsmuster zwischen Microservices.

Ereignisgesteuerte Microservice-Integration ist eine kostenlose Spring Boot 4 Microservices & REST APIs-Lektion auf CoddyKit. Dies ist Lektion 3 von 3. Du kannst die komplette Lektion unten kostenlos lesen – dann übst du sie direkt im Browser mit einem integrierten Code-Editor und einem KI-Tutor rund um die Uhr. Sie ist Teil des Spring Boot 4 Microservices & REST APIs-Lernpfads, und dein Fortschritt wird über Web und CoddyKit-App synchronisiert. Der Spring Boot 4 Microservices & REST APIs-Kurs umfasst insgesamt 3 Lektionen.

Teile dieser Lektion wurden noch nicht übersetzt und werden auf Englisch angezeigt.

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!

Häufig gestellte Fragen

Ist die Lektion „Ereignisgesteuerte Microservice-Integration“ kostenlos?

Ja — der vollständige Text von „Ereignisgesteuerte Microservice-Integration“ ist hier im Web kostenlos zu lesen. Um sie interaktiv zu üben (integrierter Code-Editor und 24/7 KI-Tutor) und den Rest des Spring Boot 4 Microservices & REST APIs-Kurses freizuschalten, upgrade auf CoddyKit PRO. Der Spring Boot 4 Microservices & REST APIs-Kurs umfasst insgesamt 3 Lektionen.

Was lerne ich in „Ereignisgesteuerte Microservice-Integration“?

Entwerfen und implementieren Sie mithilfe von Kafka asynchrone Kommunikationsmuster zwischen Microservices. Du übst Spring Boot 4 Microservices & REST APIs mit praktischem Code, den du direkt im Browser ausführst, und ein 24/7 KI-Tutor beantwortet deine Fragen während du die Lektion bearbeitest.

Brauche ich Erfahrung, um Spring Boot 4 Microservices & REST APIs zu starten?

Keine Vorkenntnisse erforderlich. Spring Boot 4 Microservices & REST APIs auf CoddyKit ist für Anfänger bis fortgeschrittene Lernende strukturiert, sodass du hier starten oder von Anfang an beginnen und in deinem eigenen Tempo voranschreiten kannst. Dies ist Lektion 3 von 3.

Wie lange dauert die Lektion „Ereignisgesteuerte Microservice-Integration“?

Die meisten CoddyKit-Lektionen dauern etwa 5–10 Minuten. Jede ist kompakt und interaktiv, sodass du stetig Fortschritte machst und genau dort weitermachst, wo du aufgehört hast – im Web und in der App.

Kann ich in dieser Spring Boot 4 Microservices & REST APIs-Lektion Code schreiben und ausführen?

Ja. Jede Spring Boot 4 Microservices & REST APIs-Lektion enthält einen integrierten Code-Editor, sodass du echten Code direkt in deinem Browser schreibst und ausführst und sofort KI-Feedback erhältst — ohne lokale Einrichtung erforderlich.

Alle Lektionen in diesem Kurs

  1. Einführung in Kafka-Produzenten
  2. Kafka-Consumer erstellen
  3. Ereignisgesteuerte Microservice-Integration
← Zurück zu Spring Boot 4 Microservices & REST APIs