Why consumers process messages in Kafka - Visual Breakdown

Process Flow - Why consumers process messages

Message produced to topic

↓

Message stored in Kafka partition

↓

Consumer polls messages

↓

Consumer processes message

↓

Consumer commits offset

↓

Ready for next message

This flow shows how a message is produced, stored, consumed, processed, and acknowledged by committing the offset.

Execution Sample

Kafka

consumer = KafkaConsumer('topic', bootstrap_servers='localhost:9092', enable_auto_commit=False)
for message in consumer:
    process(message)
    consumer.commit()

This code shows a consumer reading messages from a Kafka topic, processing each message, and committing the offset.

Process Table

Step	Action	Message Offset	Processing Status	Offset Commit Status
1	Poll message at offset 0	0	Not processed	Not committed
2	Process message at offset 0	0	Processed	Not committed
3	Commit offset 0	0	Processed	Committed
4	Poll message at offset 1	1	Not processed	Committed offset 0
5	Process message at offset 1	1	Processed	Committed offset 0
6	Commit offset 1	1	Processed	Committed
7	No more messages	-	-	-

💡 No more messages to consume, consumer waits for new messages.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	After Step 6	Final
message_offset	-	0	0	1	1	1
processing_status	Not processed	Processed	Processed	Processed	Processed	Processed
offset_commit_status	Not committed	Not committed	Committed	Committed offset 0	Committed	Committed

Key Moments - 3 Insights

Why does the consumer commit the offset after processing the message?

Committing the offset tells Kafka that the message was processed successfully, so the consumer won't reprocess it. See execution_table steps 3 and 6.

What happens if the consumer processes a message but does not commit the offset?

If the offset is not committed, Kafka will resend the message on restart, causing duplicate processing. This is why committing is important (execution_table step 2 vs 3).

Why does the consumer poll messages one by one in the flow?

Polling fetches messages from Kafka partitions in order. Processing them one by one ensures correct sequence and offset tracking (see execution_table steps 1,4).

Visual Quiz - 3 Questions

Look at the execution_table, what is the processing status at step 2?

A Committed

B Not processed

C Processed

D Polling

💡 Hint

Check the 'Processing Status' column at step 2 in the execution_table.

At which step does the consumer commit the offset for the first message?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look at the 'Offset Commit Status' column to find when it changes to 'Committed'.

If the consumer skips committing the offset, what will happen on restart?

A Messages will be lost

B Messages will be reprocessed

C Consumer will crash

D No effect

💡 Hint

Refer to key_moments about offset commit importance and execution_table steps 2 and 3.

Concept Snapshot

Kafka consumers process messages by polling from partitions.
Each message is processed in order.
After processing, the consumer commits the offset.
Committing offset prevents reprocessing on restart.
This ensures reliable and ordered message handling.

Full Transcript

In Kafka, messages are produced to topics and stored in partitions. Consumers poll these messages one by one. Each message has an offset number. The consumer processes the message and then commits the offset to Kafka. Committing the offset tells Kafka that the message was handled successfully. This prevents the consumer from processing the same message again if it restarts. The flow is: poll message, process it, commit offset, then move to the next message. This ensures messages are processed reliably and in order.