Event streaming concept in Kafka - Step-by-Step Execution

Process Flow - Event streaming concept

Event Produced

↓

Event Sent to Kafka Topic

↓

Kafka Stores Event in Partition

↓

Consumer Reads Event from Partition

↓

Consumer Processes Event

↓

Acknowledgment Sent

↓

Next Event Processed

Events are created and sent to Kafka topics, stored in partitions, then consumers read and process them in order.

Execution Sample

Kafka

producer.send('orders', {'order_id': 1, 'item': 'book'})
consumer.poll()
process(event)
consumer.commit()

A producer sends an order event to the 'orders' topic; the consumer polls, processes, and commits the event.

Process Table

Step	Action	Event Data	Kafka State	Consumer State	Output
1	Producer sends event	{order_id:1, item:'book'}	Event stored in 'orders' partition 0	No events read yet	Event queued
2	Consumer polls topic	N/A	Event still stored	Reads event from partition 0 offset 0	Event received
3	Consumer processes event	{order_id:1, item:'book'}	Event stored	Processing event	Order processed
4	Consumer commits offset	N/A	Event stored	Offset 1 committed	Ready for next event
5	No new events	N/A	No new events	No events to read	Waiting for events

💡 No new events to process, consumer waits for more.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Kafka Topic 'orders'	empty	1 event stored	1 event stored	1 event stored	1 event stored	1 event stored
Consumer Offset	0	0	0	0	1	1
Event in Consumer	none	event(order_id=1)	event(order_id=1)	event(order_id=1)	none	none

Key Moments - 3 Insights

Why does the consumer commit the offset after processing?

Committing the offset (see step 4) tells Kafka the event was processed successfully, so the consumer won't re-read it.

What happens if the consumer polls but no new events exist?

As shown in step 5, the consumer waits without processing until new events arrive.

Is the event removed from Kafka after the consumer reads it?

No, Kafka keeps events for a set time or size limit; consumers track offsets to know what to read next.

Visual Quiz - 3 Questions

Look at the execution table, what is the consumer offset after step 3?

A 1

B 0

C Not set

D Undefined

💡 Hint

Check the 'Consumer Offset' row in variable_tracker after step 3.

At which step does the consumer acknowledge it processed the event?

A Step 4

B Step 2

C Step 3

D Step 5

💡 Hint

Look for 'Offset committed' in the execution_table step 4.

If a new event arrives after step 5, what changes in the consumer state?

A Consumer offset resets to 0

B Kafka deletes old events

C Consumer reads new event from next offset

D Consumer stops polling

💡 Hint

Refer to how consumer reads events from partitions in execution_table steps 2 and 5.

Concept Snapshot

Event streaming means sending data as events to a Kafka topic.
Kafka stores events in partitions.
Consumers read events in order using offsets.
Consumers commit offsets after processing.
Events remain in Kafka until retention expires.

Full Transcript

Event streaming with Kafka works by producers sending events to topics. Kafka stores these events in partitions. Consumers poll these partitions to read events in order. After processing, consumers commit their offsets to mark progress. Kafka keeps events for a retention period, allowing multiple consumers to read independently. This flow ensures reliable, ordered event processing.

Practice

1. What is the main purpose of event streaming in Kafka?

easy

A. To batch process data once a day

B. To store data permanently in a database

C. To create static reports from data

D. To send data as it happens for real-time updates

Solution

1. Step 1: Understand event streaming concept

   Event streaming means sending data continuously as events happen, not waiting to batch or store permanently.

2. Step 2: Match purpose with options

   Only To send data as it happens for real-time updates describes sending data as it happens for real-time updates, which is the core of event streaming.

3. Final Answer:

   To send data as it happens for real-time updates -> Option D

4. Quick Check:

   Event streaming = real-time data flow [OK]

Hint: Event streaming means data flows live, not stored or batched [OK]

Common Mistakes:

• Confusing event streaming with batch processing
• Thinking event streaming stores data permanently
• Assuming event streaming creates static reports

2. Which of the following is the correct way to describe a Kafka producer?

easy

A. A database that stores events permanently

B. A component that reads events from topics

C. A component that sends events to topics

D. A tool that visualizes event data

Solution

1. Step 1: Define Kafka producer role

   A Kafka producer is the part that sends or writes events into Kafka topics.

2. Step 2: Compare options with definition

   A component that sends events to topics correctly states the producer sends events to topics; others describe consumers, databases, or tools.

3. Final Answer:

   A component that sends events to topics -> Option C

4. Quick Check:

   Producer = sends events [OK]

Hint: Producer sends events; consumer reads events [OK]

Common Mistakes:

• Mixing up producer and consumer roles
• Thinking producer stores data permanently
• Confusing producer with visualization tools

3. Given this Kafka event flow: Producer sends events to topic 'orders'. Consumer reads from 'orders'. What happens if the consumer is slow?

medium

A. Events are lost immediately

B. Events accumulate in the topic until consumed

C. Producer stops sending events

D. Topic deletes old events instantly

Solution

1. Step 1: Understand Kafka topic behavior

   Kafka stores events in topics until consumers read them; slow consumers cause events to accumulate.

2. Step 2: Analyze options based on behavior

   Events accumulate in the topic until consumed matches this behavior; events wait in topic. Events are not lost immediately, producer keeps sending, and topic deletes old events only after retention period.

3. Final Answer:

   Events accumulate in the topic until consumed -> Option B

4. Quick Check:

   Slow consumer = event backlog in topic [OK]

Hint: Slow consumer causes event backlog, not loss [OK]

Common Mistakes:

• Assuming events are lost if consumer is slow
• Thinking producer stops sending events
• Believing topics delete events instantly

4. You wrote a Kafka consumer but it never receives any events. Which is the most likely mistake?

medium

A. The consumer is subscribed to the wrong topic

B. The producer is sending events correctly

C. The topic has too many partitions

D. The consumer is reading from the correct topic

Solution

1. Step 1: Identify why consumer gets no events

   If a consumer never receives events, a common cause is subscribing to the wrong topic.

2. Step 2: Evaluate options

   The consumer is subscribed to the wrong topic points to wrong topic subscription, which explains no events. Other options do not explain lack of events.

3. Final Answer:

   The consumer is subscribed to the wrong topic -> Option A

4. Quick Check:

   No events = wrong topic subscription [OK]

Hint: Check consumer topic subscription first [OK]

Common Mistakes:

• Ignoring topic subscription errors
• Blaming producer when it sends correctly
• Confusing topic partitions with event delivery

5. You want to build a real-time dashboard that updates instantly when new sales happen. Which Kafka setup best supports this?

hard

A. Producer sends sales events to a topic; consumer reads and updates dashboard immediately

B. Producer batches sales events daily; consumer reads once a day

C. Producer sends events to multiple unrelated topics; consumer reads only one

D. Consumer writes sales events back to producer

Solution

1. Step 1: Identify real-time update needs

   A real-time dashboard requires events sent and consumed instantly to update live.

2. Step 2: Match Kafka setup to real-time flow

   Producer sends sales events to a topic; consumer reads and updates dashboard immediately describes producer sending events to a topic and consumer reading immediately to update dashboard, fitting real-time needs.

3. Step 3: Eliminate other options

   Producer batches sales events daily; consumer reads once a day is batch, not real-time; C is inconsistent topic usage; D is incorrect flow direction.

4. Final Answer:

   Producer sends sales events to a topic; consumer reads and updates dashboard immediately -> Option A

5. Quick Check:

   Real-time dashboard = immediate event flow [OK]

Hint: Real-time needs immediate produce and consume flow [OK]

Common Mistakes:

• Choosing batch processing for real-time needs
• Using multiple unrelated topics incorrectly
• Confusing producer and consumer roles