Producer API basics in Kafka - Time & Space Complexity

Time Complexity: Producer API basics

O(n)

Understanding Time Complexity

When sending messages with Kafka's Producer API, it's important to know how the time to send grows as you send more messages.

We want to understand how the number of messages affects the work the producer does.

Scenario Under Consideration

Analyze the time complexity of the following Kafka producer code snippet.

import org.apache.kafka.clients.producer.KafkaProducer;
import org.apache.kafka.clients.producer.ProducerRecord;

KafkaProducer<String, String> producer = new KafkaProducer<>(props);

for (int i = 0; i < n; i++) {
    ProducerRecord<String, String> record = new ProducerRecord<>("topic", "key" + i, "value" + i);
    producer.send(record);
}
producer.close();

This code sends n messages to a Kafka topic, one by one, using the producer's send method.

Identify Repeating Operations

Look at what repeats as the input grows.

• Primary operation: The for loop that sends each message.
• How many times: Exactly n times, once per message.

How Execution Grows With Input

As you increase the number of messages, the work grows in a simple way.

Input Size (n)	Approx. Operations
10	10 sends
100	100 sends
1000	1000 sends

Pattern observation: The number of send operations grows directly with the number of messages.

Final Time Complexity

Time Complexity: O(n)

This means the time to send messages grows in a straight line with how many messages you send.

Common Mistake

[X] Wrong: "Sending multiple messages at once is always faster and has constant time complexity."

[OK] Correct: Even if you batch messages, the total work still grows with the number of messages, so time complexity depends on n.

Interview Connect

Understanding how sending messages scales helps you explain how your code handles more data smoothly and efficiently.

Self-Check

"What if we used asynchronous sends with callbacks instead of synchronous sends? How would the time complexity change?"