Concorrência e gerenciamento de threads
Configure e gerencie a concorrência de consumidores em aplicações Spring Boot com Kafka para otimizar o rendimento e a utilização de recursos.
Concorrência e gerenciamento de threads é uma aula grátis de Advanced Spring Boot 4: Event-Driven Architecture (Kafka) no CoddyKit. Esta é a aula 3 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.
Boosting Consumer Throughput
When consuming messages from Kafka, processing them sequentially might not be fast enough. Concurrency allows your application to process multiple messages in parallel, significantly increasing throughput.
This is crucial for high-volume topics where messages arrive rapidly and need quick processing.
Default Consumer Behavior
By default, a @KafkaListener method in Spring Boot will create one consumer thread per listener container. This single thread is responsible for fetching and processing messages from the partitions assigned to it.
While simple, this setup doesn't always leverage multi-core processors for parallel message processing from a single topic effectively.
The `concurrency` Property
Spring for Apache Kafka provides a powerful concurrency property that allows you to specify the number of consumer threads to run for a given listener.
- Each concurrent consumer runs in its own thread.
- These threads collectively manage the partitions assigned to the consumer group.
This is key to scaling your consumer horizontally within a single application instance.
Setting Concurrency Level
You can set the concurrency level directly on the @KafkaListener annotation or globally via configuration properties.
For example, @KafkaListener(topics = "my-topic", groupId = "my-group", concurrency = "3") will start 3 consumer threads.
Alternatively, you can set it in application.properties for all listeners using a specific container factory.
Concurrency in Action
Let's see how to configure a listener with concurrency. This listener will process messages from "my-topic" using 3 concurrent threads.
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 ConcurrencyApp {
public static void main(String[] args) {
SpringApplication.run(ConcurrencyApp.class, args);
}
@Component
static class MyKafkaListener {
@KafkaListener(topics = "my-topic", groupId = "my-group", concurrency = "3")
public void listen(String message) {
System.out.println("Thread " + Thread.currentThread().getId() +
" received: " + message);
}
}
}How Threads are Managed
Spring Kafka uses ConcurrentKafkaListenerContainerFactory to create and manage the underlying consumer threads. When you set concurrency, this factory creates that many KafkaMessageListenerContainer instances.
Each container manages one consumer instance, which in turn is assigned a subset of topic partitions.
Advanced Thread Pool Customization
For more fine-grained control, you can customize the thread pool used by the container factory. This involves creating your own ConcurrentKafkaListenerContainerFactory bean.
You can set properties like max.poll.records and max.poll.interval.ms to optimize how many messages each consumer fetches and how often it commits offsets.
Partitions and Concurrency
The effective concurrency for a consumer group is limited by the number of partitions in the topic. Kafka guarantees that messages within a single partition are processed in order.
- If you have 5 partitions and set
concurrency = 10, only 5 threads will be active (one per partition). - It's best practice to set
concurrencyto be less than or equal to the number of topic partitions.
Key Concurrency Considerations
While concurrency boosts throughput, keep these in mind:
- Order: Messages within a single partition are ordered, but overall order across partitions is NOT guaranteed.
- Resource Usage: More threads mean more memory and CPU. Monitor your application's resources.
- Rebalancing: High concurrency can lead to more frequent consumer rebalances if not managed well.
Concurrency Quiz
Imagine a Kafka topic named "orders" with 4 partitions. A Spring Boot application has a @KafkaListener configured for this topic within a consumer group. If the concurrency property is set to 6, how many consumer threads will actively process messages from the "orders" topic?
Concurrency Recap
In this lesson, we explored how to manage consumer concurrency in Spring Boot Kafka applications. We learned about the concurrency property, how it relates to topic partitions, and key considerations for using it effectively.
By configuring concurrency, you can significantly optimize your application's throughput and resource utilization for high-volume event processing.
Perguntas Frequentes
A aula “Concorrência e gerenciamento de threads” é grátis?
Sim — o texto completo de “Concorrência e gerenciamento de threads” é 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 “Concorrência e gerenciamento de threads”?
Configure e gerencie a concorrência de consumidores em aplicações Spring Boot com Kafka para otimizar o rendimento e a utilização de recursos. 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 3 de 4.
Quanto tempo leva a aula “Concorrência e gerenciamento de threads”?
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
- Confirmação manual de deslocamentos
- Pausando e retomando consumidores
- Concorrência e gerenciamento de threads
- Ouvintes de rebalanceamento e associação estática