Consumer-Gruppen verwalten
Verstehen Sie, wie Consumer-Gruppen parallele Verarbeitung und Fehlertoleranz ermöglichen und sicherstellen, dass Nachrichten pro Gruppe nur einmal verarbeitet werden.
Consumer-Gruppen verwalten ist eine kostenlose Advanced Spring Boot 4: Event-Driven Architecture (Kafka)-Lektion auf CoddyKit. Dies ist Lektion 2 von 4. 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 Advanced Spring Boot 4: Event-Driven Architecture (Kafka)-Lernpfads, und dein Fortschritt wird über Web und CoddyKit-App synchronisiert. Der Advanced Spring Boot 4: Event-Driven Architecture (Kafka)-Kurs umfasst insgesamt 4 Lektionen.
Teile dieser Lektion wurden noch nicht übersetzt und werden auf Englisch angezeigt.
What are Consumer Groups?
Welcome! Today, we'll explore Consumer Groups in Kafka. These are a core concept for scaling message consumption and ensuring fault tolerance.
Think of a consumer group as a team of consumers working together to process messages from one or more topics. Each message from a topic's partitions is delivered to only one consumer within that specific group.
Scaling & Fault Tolerance
Consumer groups solve two major challenges:
- Scaling: By distributing partitions across multiple consumers, you can process messages much faster, increasing your application's throughput.
- Fault Tolerance: If a consumer fails or leaves the group, Kafka automatically reassigns its partitions to other active consumers in the same group. This ensures continuous message processing.
Ultimately, a message is processed exactly once per consumer group, even with multiple consumers.
Partitions & Consumers
To understand groups, remember that Kafka topics are divided into partitions. These partitions are the unit of parallelism.
- Within a consumer group, each partition is assigned to at most one consumer.
- If you have more consumers than partitions in a group, some consumers will be idle.
- If you have fewer consumers than partitions, some consumers will handle multiple partitions.
This assignment strategy ensures ordered processing within each partition while allowing parallel processing across partitions.
Dynamic Partition Rebalancing
Kafka is smart! When a consumer joins or leaves a group (e.g., an application starts, stops, or crashes), Kafka automatically triggers a rebalance.
During a rebalance, partitions are dynamically re-assigned among the active consumers in the group. This ensures all partitions continue to be consumed and adapts to changes in your application's scaling needs.
Rebalancing is an automatic process that guarantees high availability and adapts to fluctuating workloads.
`group.id` in Spring Kafka
In Spring Kafka, you define which consumer group your listener belongs to using the group.id property.
This unique string identifies your consumer group to Kafka. All consumers (whether in the same application instance or different instances) that share the exact same group.id are considered part of the same group.
You typically configure this in your application.properties or directly in the @KafkaListener annotation.
Spring Listener Example
Here's a basic Spring Boot Kafka listener configured with a specific group.id. This tells Kafka that this listener is part of the 'my-first-group' consumer group.
Try running this example and observe the output!
package com.coddykit;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.kafka.annotation.KafkaListener;
import org.springframework.stereotype.Component;
@SpringBootApplication
public class ConsumerGroupApp {
public static void main(String[] args) {
SpringApplication.run(ConsumerGroupApp.class, args);
}
@Component
public static class MyKafkaListener {
@KafkaListener(topics = "my-topic", groupId = "my-first-group")
public void listen(String message) {
System.out.println("Received in Group 1: " + message);
}
}
}Scaling with Multiple Consumers
To achieve parallel processing and higher throughput for a topic, you can run multiple instances of your application, all configured with the same group.id.
Kafka will then distribute the topic's partitions across these running instances. Each instance will process a subset of the partitions independently, effectively scaling out your message consumption.
This is the primary way to handle high-volume topics efficiently.
Multiple Listeners, Same Group
You can also define multiple @KafkaListener methods within the same Spring Boot application instance, all belonging to the same consumer group.
Spring Kafka manages these as separate consumers within that group. If the topic has enough partitions, these listeners can process messages from different partitions in parallel within a single application.
The id attribute helps differentiate listener beans, especially when multiple listeners are defined for the same topic and group.
package com.coddykit;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.kafka.annotation.KafkaListener;
import org.springframework.stereotype.Component;
@SpringBootApplication
public class MultiListenerApp {
public static void main(String[] args) {
SpringApplication.run(MultiListenerApp.class, args);
}
@Component
public static class MyMultiKafkaListeners {
// Consumer 1 for "my-topic" in "my-app-group"
@KafkaListener(topics = "my-topic", groupId = "my-app-group", id = "listener1")
public void listen1(String message) {
System.out.println("Listener 1 received: " + message);
}
// Consumer 2 for "my-topic" in "my-app-group"
@KafkaListener(topics = "my-topic", groupId = "my-app-group", id = "listener2")
public void listen2(String message) {
System.out.println("Listener 2 received: " + message);
}
}
}Independent Consumption
What if different applications need to process the same messages from a topic, but for different purposes?
This is where multiple consumer groups come in handy. You can have several distinct consumer groups, each with its own unique group.id, consuming from the same Kafka topic.
Each group will receive a full copy of all messages published to that topic. This allows for independent processing without affecting other groups.
Group Management Check
Consider a Kafka topic with 3 partitions. You start an application with one consumer group and two active consumers. How will messages be distributed?
Consumer Group Summary
You've learned about the power of Kafka Consumer Groups!
- They are crucial for scaling message consumption and building fault-tolerant applications.
- Messages from a topic's partitions are distributed among consumers in a group, processed exactly once per group.
- Kafka handles partition assignment and rebalancing automatically as consumers join or leave.
- Using different
group.idvalues enables multiple applications to independently consume the same stream of messages.
Mastering consumer groups is key to building robust Kafka applications.
Lerne Advanced Spring Boot 4: Event-Driven Architecture (Kafka) mit einem KI-Tutor — kostenlos
Schreibe und führe echten Code in deinem Browser aus, bekomme sofortige Hilfe von einem 24/7 KI-Tutor und setze dein Lernen im Web oder in der App fort.
- Kurse
- 12
- Lektionen
- 48
Häufig gestellte Fragen
Ist die Lektion „Consumer-Gruppen verwalten“ kostenlos?
Ja — der vollständige Text von „Consumer-Gruppen verwalten“ ist hier im Web kostenlos zu lesen. Um sie interaktiv zu üben (integrierter Code-Editor und 24/7 KI-Tutor) und den Rest des Advanced Spring Boot 4: Event-Driven Architecture (Kafka)-Kurses freizuschalten, upgrade auf CoddyKit PRO. Der Advanced Spring Boot 4: Event-Driven Architecture (Kafka)-Kurs umfasst insgesamt 4 Lektionen.
Was lerne ich in „Consumer-Gruppen verwalten“?
Verstehen Sie, wie Consumer-Gruppen parallele Verarbeitung und Fehlertoleranz ermöglichen und sicherstellen, dass Nachrichten pro Gruppe nur einmal verarbeitet werden. Du übst Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 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 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) zu starten?
Keine Vorkenntnisse erforderlich. Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 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 2 von 4.
Wie lange dauert die Lektion „Consumer-Gruppen verwalten“?
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 Advanced Spring Boot 4: Event-Driven Architecture (Kafka)-Lektion Code schreiben und ausführen?
Ja. Jede Advanced Spring Boot 4: Event-Driven Architecture (Kafka)-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
- Kafka-Listener-Container erstellen
- Consumer-Gruppen verwalten
- Deserialisierung und Nachrichtenkonvertierung
- Batch-Verarbeitung und Acknowledgment-Modi