Kafka integration basics in Spring Boot - Performance & Optimization

Performance: Kafka integration basics

MEDIUM IMPACT

This affects the responsiveness and throughput of message processing in a web application, impacting how quickly data flows between services.

Consuming Kafka messages in a Spring Boot app

Spring Boot

@KafkaListener(topics = "topicName")
public void consumeAsync(String message) {
  CompletableFuture.runAsync(() -> processMessage(message));
}

Processes messages asynchronously, freeing the consumer thread to handle new messages immediately.

📈 Performance Gainimproves throughput and responsiveness, reducing INP

Consuming Kafka messages in a Spring Boot app

Spring Boot

public void consume(String message) {
  // process message synchronously
  processMessage(message);
  // blocks main thread
}

Processing messages synchronously blocks the consumer thread, reducing throughput and increasing latency.

📉 Performance Costblocks message consumption, increasing INP and causing slower response to new messages

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous Kafka message processing	N/A	N/A	N/A	[X] Bad
Asynchronous Kafka message processing	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

Kafka integration affects the backend message handling pipeline rather than browser rendering, but it impacts user experience by controlling how fast data updates reach the frontend.

→Message Polling

→Message Processing

→Thread Management

⚠️ BottleneckSynchronous processing blocking consumer threads

Core Web Vital Affected

INP

This affects the responsiveness and throughput of message processing in a web application, impacting how quickly data flows between services.

Optimization Tips

1Avoid synchronous message processing in Kafka consumers to prevent blocking.

2Tune Kafka consumer poll intervals to balance latency and resource use.

3Use asynchronous processing to improve message throughput and responsiveness.

Performance Quiz - 3 Questions

What is a performance downside of processing Kafka messages synchronously in the consumer thread?

A It increases the bundle size of the frontend application.

B It blocks the consumer thread, reducing throughput and increasing latency.

C It causes layout shifts in the browser.

D It improves message processing speed.

DevTools: Performance

How to check: Use backend profiling tools or Spring Boot actuator metrics to monitor Kafka consumer thread usage and message processing latency.

What to look for: Look for thread blocking times and message processing delays to identify bottlenecks.

Practice

1. What is the primary purpose of @KafkaListener in a Spring Boot application?

easy

A. To listen and consume messages from a Kafka topic

B. To send messages to a Kafka topic

C. To configure Kafka broker settings

D. To create new Kafka topics automatically

Solution

1. Step 1: Understand the role of @KafkaListener

   This annotation marks a method to receive messages from a Kafka topic automatically.

2. Step 2: Differentiate sending and listening

   Sending messages is done with KafkaTemplate, not @KafkaListener.

3. Final Answer:

   To listen and consume messages from a Kafka topic -> Option A

4. Quick Check:

   @KafkaListener listens to topics [OK]

Hint: Remember: Listener receives, Template sends [OK]

Common Mistakes:

• Confusing @KafkaListener with KafkaTemplate
• Thinking @KafkaListener creates topics
• Assuming it configures Kafka brokers

2. Which of the following is the correct way to send a message to a Kafka topic using Spring Boot?

easy

A. new KafkaProducer().send("topicName", "message")

B. @KafkaListener(topic = "topicName")

C. KafkaTemplate.listen("topicName", "message")

D. kafkaTemplate.send("topicName", "message")

Solution

1. Step 1: Identify the sending method in Spring Boot

   Spring Boot uses KafkaTemplate with the send() method to send messages.

2. Step 2: Check syntax correctness

   kafkaTemplate.send("topicName", "message") is the correct syntax to send a message.

3. Final Answer:

   kafkaTemplate.send("topicName", "message") -> Option D

4. Quick Check:

   Sending uses KafkaTemplate.send() [OK]

Hint: Send messages with kafkaTemplate.send() [OK]

Common Mistakes:

• Using @KafkaListener to send messages
• Calling listen() instead of send()
• Instantiating KafkaProducer manually in Spring Boot

3. Given this Spring Boot Kafka listener method:

@KafkaListener(topics = "myTopic")
public void listen(String message) {
    System.out.println("Received: " + message);
}

What will be printed if a message "Hello Kafka" is sent to myTopic?

medium

A. Received: Hello Kafka

B. Hello Kafka

C. Received message: Hello Kafka

D. Error: No message received

Solution

1. Step 1: Analyze the listener method output

   The method prints "Received: " concatenated with the message string.

2. Step 2: Substitute the message value

   Message is "Hello Kafka", so output is "Received: Hello Kafka".

3. Final Answer:

   Received: Hello Kafka -> Option A

4. Quick Check:

   Prints "Received: " + message [OK]

Hint: Check print statement format carefully [OK]

Common Mistakes:

• Ignoring the prefix in the print statement
• Assuming only the message prints
• Confusing topic name with output

4. Consider this Spring Boot Kafka configuration snippet:

@Bean
public NewTopic topic() {
    return new NewTopic("testTopic", 1, (short) 1);
}

What is the likely error if the application fails to create the topic?

medium

A. Incorrect topic name format

B. Missing Kafka broker connection settings

C. NewTopic requires 3 parameters but only 2 provided

D. NewTopic bean must be annotated with @KafkaListener

Solution

1. Step 1: Understand NewTopic bean usage

   NewTopic defines topic name, partitions, and replication factor correctly here.

2. Step 2: Identify common cause for topic creation failure

   Failure usually happens if Kafka broker connection settings are missing or incorrect.

3. Final Answer:

   Missing Kafka broker connection settings -> Option B

4. Quick Check:

   Broker settings needed for topic creation [OK]

Hint: Check Kafka broker config if topic creation fails [OK]

Common Mistakes:

• Thinking @KafkaListener is needed on NewTopic bean
• Assuming topic name format is invalid
• Miscounting NewTopic constructor parameters

5. You want to create a Spring Boot Kafka consumer that listens to two topics: topicA and topicB. Which of the following @KafkaListener annotations correctly achieves this?

hard

A. @KafkaListener(topics = "topicA, topicB")

B. @KafkaListener(topic = "topicA,topicB")

C. @KafkaListener(topics = {"topicA", "topicB"})

D. @KafkaListener(topics = ["topicA", "topicB"])

Solution

1. Step 1: Recall correct syntax for multiple topics

   Spring Boot expects an array of strings for multiple topics: topics = {"topicA", "topicB"}.

2. Step 2: Evaluate other options

   @KafkaListener(topic = "topicA,topicB") uses wrong attribute name and comma string, C uses string with comma but not array, D uses invalid syntax with square brackets.

3. Final Answer:

   @KafkaListener(topics = {"topicA", "topicB"}) -> Option C

4. Quick Check:

   Multiple topics require array syntax [OK]

Hint: Use curly braces for multiple topics in @KafkaListener [OK]

Common Mistakes:

• Using comma-separated string instead of array
• Wrong attribute name 'topic' instead of 'topics'
• Using square brackets instead of curly braces