Construção de contêineres de ouvintes do Kafka
Crie métodos `@KafkaListener` para consumir automaticamente mensagens dos tópicos especificados e configurar suas propriedades.
Construção de contêineres de ouvintes do Kafka é uma aula grátis de Advanced Spring Boot 4: Event-Driven Architecture (Kafka) no CoddyKit. Esta é a aula 1 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Advanced Spring Boot 4: Event-Driven Architecture (Kafka), e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Advanced Spring Boot 4: Event-Driven Architecture (Kafka) inclui 4 aulas no total.
Partes desta aula ainda não foram traduzidas e aparecem em inglês.
Welcome to Kafka Consumers!
In event-driven systems, producers send events, and consumers react to them. Spring Boot makes it easy to build Kafka consumers.
We'll learn how to create methods that automatically listen for and process messages from Kafka topics using the @KafkaListener annotation.
The @KafkaListener Annotation
The @KafkaListener annotation is the core of consuming messages in Spring Boot. You place it on a method, telling Spring which Kafka topic(s) to listen to.
- It automatically sets up the necessary infrastructure.
- The method parameter receives the message payload.
- You must specify a
topicsandgroupId.
Basic Listener: String Messages
Let's create a simple Kafka listener that consumes plain string messages. Remember, you'd typically have Kafka dependencies and configuration in your Spring Boot project.
Here, my-topic is the Kafka topic, and my-group is the consumer group ID.
package com.example.kafkaconsumer;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.kafka.annotation.EnableKafka;
import org.springframework.kafka.annotation.KafkaListener;
import org.springframework.stereotype.Component;
@SpringBootApplication
@EnableKafka
public class KafkaConsumerApplication {
public static void main(String[] args) {
// In a real app, SpringApplication.run() starts the context
// and registers the @KafkaListener methods.
System.out.println("Spring Boot Kafka Consumer App Started (simulated)");
// For a runnable snippet, we just show the listener logic.
// In a full app, this would run indefinitely, waiting for messages.
}
}
@Component
class MyStringListener {
@KafkaListener(topics = "my-topic", groupId = "my-group")
public void listen(String message) {
System.out.println("Received String: " + message);
}
}Understanding Consumer Groups
The groupId property is crucial for Kafka consumers. It defines a group of consumers that work together to process messages from one or more topics.
- Load Balancing: Messages from a topic are distributed among consumers in the same group.
- Fault Tolerance: If a consumer fails, another in the group takes over its partitions.
- Unique Processing: Each message is processed by only one consumer within a group.
Listening to Multiple Topics
A single @KafkaListener method can listen to multiple topics. You can specify them as an array of strings in the topics attribute.
This is useful when different topics carry related types of messages that can be handled by the same logic.
package com.example.kafkaconsumer;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.kafka.annotation.EnableKafka;
import org.springframework.kafka.annotation.KafkaListener;
import org.springframework.stereotype.Component;
@SpringBootApplication
@EnableKafka
public class KafkaConsumerApplication {
public static void main(String[] args) {
System.out.println("Spring Boot Kafka Consumer App Started (simulated)");
}
}
@Component
class MultiTopicListener {
@KafkaListener(topics = {"topic-a", "topic-b"}, groupId = "multi-group")
public void listenMultipleTopics(String message) {
System.out.println("Received from multiple topics: " + message);
}
}Receiving Custom Objects
Kafka messages often contain structured data, not just strings. Spring Kafka can automatically convert JSON or Avro messages into Java objects (POJOs).
You just need to define a POJO that matches the structure of your Kafka messages and use it as the method parameter.
Code: Custom Object Listener
Here's how to set up a listener for a custom MyEvent object. Spring Boot handles the deserialization, assuming you have the correct deserializer configured (e.g., JSON deserializer).
package com.example.kafkaconsumer;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.kafka.annotation.EnableKafka;
import org.springframework.kafka.annotation.KafkaListener;
import org.springframework.stereotype.Component;
// A simple data class representing an event
class MyEvent {
private String id;
private String description;
// Getters and setters are essential for deserialization
public String getId() { return id; }
public void setId(String id) { this.id = id; }
public String getDescription() { return description; }
public void setDescription(String description) { this.description = description; }
@Override
public String toString() {
return "MyEvent{id='" + id + "', description='" + description + "'}";
}
}
@SpringBootApplication
@EnableKafka
public class KafkaConsumerApplication {
public static void main(String[] args) {
System.out.println("Spring Boot Kafka Consumer App Started (simulated)");
}
}
@Component
class MyObjectListener {
@KafkaListener(topics = "object-topic", groupId = "object-group")
public void listenObject(MyEvent event) {
System.out.println("Received object: " + event);
}
}Accessing Message Metadata
Beyond the message payload, Kafka messages carry useful metadata like topic, partition, offset, and headers. You can access these in your listener method:
@Payload: The message body (default).@Header: Access specific Kafka headers.ConsumerRecord: The raw Kafka record, giving access to all metadata.
package com.example.kafkaconsumer;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.kafka.annotation.EnableKafka;
import org.springframework.kafka.annotation.KafkaListener;
import org.springframework.messaging.handler.annotation.Header;
import org.springframework.messaging.handler.annotation.Payload;
import org.springframework.stereotype.Component;
@SpringBootApplication
@EnableKafka
public class KafkaConsumerApplication {
public static void main(String[] args) {
System.out.println("Spring Boot Kafka Consumer App Started (simulated)");
}
}
@Component
class MyMetadataListener {
@KafkaListener(topics = "metadata-topic", groupId = "meta-group")
public void listenWithMetadata(
@Payload String message,
@Header("kafka_receivedTopic") String topic,
@Header("kafka_receivedPartitionId") int partition,
@Header("kafka_offset") long offset) {
System.out.println("Topic: " + topic + ", Partition: " + partition + ", Offset: " + offset);
System.out.println("Message: " + message);
}
}Configuring Listener Properties
While @KafkaListener handles many defaults, you can customize consumer behavior. Properties like bootstrap.servers, auto.offset.reset, and key.deserializer are typically set in your application.properties or application.yml file.
- Spring Boot automatically picks up these configurations.
- They apply to all
@KafkaListeners unless overridden.
Test Your Kafka Listener Knowledge!
Which of the following statements about Spring Boot's @KafkaListener annotation is TRUE?
Recap: Building Kafka Listeners
You've taken the first step into consuming Kafka messages with Spring Boot!
- The
@KafkaListenerannotation simplifies consumer creation. - You specify topics and a
groupIdto organize consumers. - Listeners can handle String messages, custom objects, and access metadata.
- Configuration is often managed through
application.properties.
Next, we'll explore how consumer groups work in more detail to achieve scalable and fault-tolerant message processing!
Perguntas Frequentes
A aula “Construção de contêineres de ouvintes do Kafka” é grátis?
Sim — o texto completo de “Construção de contêineres de ouvintes do Kafka” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Advanced Spring Boot 4: Event-Driven Architecture (Kafka), atualize para CoddyKit PRO. O curso de Advanced Spring Boot 4: Event-Driven Architecture (Kafka) inclui 4 aulas no total.
O que vou aprender em “Construção de contêineres de ouvintes do Kafka”?
Crie métodos `@KafkaListener` para consumir automaticamente mensagens dos tópicos especificados e configurar suas propriedades. Você pratica Advanced Spring Boot 4: Event-Driven Architecture (Kafka) com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.
Preciso ter experiência prévia para começar Advanced Spring Boot 4: Event-Driven Architecture (Kafka)?
Nenhuma experiência prévia é necessária. Advanced Spring Boot 4: Event-Driven Architecture (Kafka) no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 1 de 4.
Quanto tempo leva a aula “Construção de contêineres de ouvintes do Kafka”?
A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.
Posso escrever e executar código nesta aula de Advanced Spring Boot 4: Event-Driven Architecture (Kafka)?
Sim. Cada aula de Advanced Spring Boot 4: Event-Driven Architecture (Kafka) inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.
Todas as aulas deste curso
- Construção de contêineres de ouvintes do Kafka
- Gerenciamento de grupos de consumidores
- Desserialização e conversão de mensagens
- Consumo em lote e modos de confirmação