Why event-driven scales applications in Kafka - See It in Action

Why Event-Driven Architecture Scales Applications

📖 Scenario: Imagine you are building a simple online store system. When a customer places an order, the system needs to process the order, update inventory, and notify the shipping department. Using event-driven architecture with Kafka helps the system handle many orders smoothly without slowing down.

🎯 Goal: Build a simple event-driven flow using Kafka concepts to understand how it helps scale applications by decoupling parts of the system.

📋 What You'll Learn

Create a Kafka topic called orders to hold order events

Create a producer that sends order messages to the orders topic

Create a consumer that listens to the orders topic and processes orders

Print the processed order details to show the flow

💡 Why This Matters

🌍 Real World

Event-driven systems like this are used in online stores, banking, and social media to handle many actions happening at once without slowing down.

💼 Career

Understanding event-driven architecture and Kafka is valuable for backend developers, system architects, and anyone working on scalable, reliable software systems.

1

Create the Kafka topic for orders

Write code to create a Kafka topic named orders that will hold order events.

Kafka

# Your code here to create the 'orders' topic

Hint

Use NewTopic with name orders, 3 partitions, and replication factor 1.

2

Create a producer to send order events

Write code to create a Kafka producer that sends an order message with key order1 and value {"item": "book", "quantity": 2} to the orders topic.

Kafka

from kafka.admin import KafkaAdminClient, NewTopic

admin_client = KafkaAdminClient(bootstrap_servers="localhost:9092")

orders_topic = NewTopic(name="orders", num_partitions=3, replication_factor=1)

admin_client.create_topics(new_topics=[orders_topic], validate_only=False)

# Your code here to create a producer and send one order message

Hint

Create a KafkaProducer with JSON serialization and send the order message with key order1.

3

Create a consumer to process order events

Write code to create a Kafka consumer that listens to the orders topic, reads messages, and stores them in a list called processed_orders.

Kafka

from kafka.admin import KafkaAdminClient, NewTopic
from kafka import KafkaProducer, KafkaConsumer
import json

admin_client = KafkaAdminClient(bootstrap_servers="localhost:9092")

orders_topic = NewTopic(name="orders", num_partitions=3, replication_factor=1)

admin_client.create_topics(new_topics=[orders_topic], validate_only=False)

producer = KafkaProducer(bootstrap_servers='localhost:9092', value_serializer=lambda v: json.dumps(v).encode('utf-8'), key_serializer=lambda k: k.encode('utf-8'))

order_message = {"item": "book", "quantity": 2}

producer.send('orders', key='order1', value=order_message)
producer.flush()

# Your code here to create a consumer and collect processed orders

Hint

Create a KafkaConsumer subscribed to orders and append messages to processed_orders.

4

Print the processed orders

Write code to print the processed_orders list to show the processed order details.

Kafka

from kafka.admin import KafkaAdminClient, NewTopic
from kafka import KafkaProducer, KafkaConsumer
import json

admin_client = KafkaAdminClient(bootstrap_servers="localhost:9092")

orders_topic = NewTopic(name="orders", num_partitions=3, replication_factor=1)

admin_client.create_topics(new_topics=[orders_topic], validate_only=False)

producer = KafkaProducer(bootstrap_servers='localhost:9092', value_serializer=lambda v: json.dumps(v).encode('utf-8'), key_serializer=lambda k: k.encode('utf-8'))

order_message = {"item": "book", "quantity": 2}

producer.send('orders', key='order1', value=order_message)
producer.flush()

consumer = KafkaConsumer('orders', bootstrap_servers='localhost:9092', auto_offset_reset='earliest', group_id='order_group', value_deserializer=lambda v: json.loads(v.decode('utf-8')), key_deserializer=lambda k: k.decode('utf-8'))

processed_orders = []

for message in consumer:
    processed_orders.append({'key': message.key, 'value': message.value})
    break

# Your code here to print processed_orders

Hint

Use print(processed_orders) to show the list of processed orders.

Practice

1. What is the main reason event-driven architecture helps applications scale better?

easy

A. It forces all parts of the app to run in a single sequence.

B. It stores all data in one central database for faster access.

C. It allows different parts of the app to work independently by sending messages.

D. It requires fewer servers to run the app.

Solution

1. Step 1: Understand event-driven independence

   Event-driven design lets parts of an app send messages and work independently without waiting for each other.

2. Step 2: Connect independence to scaling

   This independence means tasks can run at the same time, helping the app handle more work smoothly as it grows.

3. Final Answer:

   It allows different parts of the app to work independently by sending messages. -> Option C

4. Quick Check:

   Event-driven = Independent parts = Scales well [OK]

Hint: Event-driven means parts work alone and talk by messages [OK]

Common Mistakes:

• Thinking event-driven forces sequential processing
• Believing event-driven centralizes all data
• Assuming event-driven reduces server count automatically

2. Which Kafka component is responsible for storing and distributing messages in an event-driven system?

easy

A. Broker

B. Producer

C. Consumer

D. Zookeeper

Solution

1. Step 1: Identify Kafka components roles

   Producer sends messages, Consumer reads messages, Broker stores and distributes messages, Zookeeper manages cluster metadata.

2. Step 2: Match storage and distribution role

   The Broker is the Kafka server that stores messages and sends them to consumers.

3. Final Answer:

   Broker -> Option A

4. Quick Check:

   Broker = Stores and distributes messages [OK]

Hint: Broker stores and sends messages in Kafka [OK]

Common Mistakes:

• Confusing Producer as storage
• Thinking Consumer stores messages
• Assuming Zookeeper handles message storage

3. Given this Kafka event-driven flow:

Producer sends 3 messages: M1, M2, M3
Consumer processes messages asynchronously

What is the expected order of message processing by the consumer?

medium

A. Messages may be processed in any order depending on consumer speed

B. M3, M2, M1 always in reverse order

C. M1, M2, M3 always in order

D. Only M1 is processed, others are ignored

Solution

1. Step 1: Understand asynchronous processing

   Consumers process messages independently and may handle them at different speeds.

2. Step 2: Analyze message order in async processing

   Because processing is asynchronous, messages can be handled in any order, not necessarily the order sent.

3. Final Answer:

   Messages may be processed in any order depending on consumer speed -> Option A

4. Quick Check:

   Async consumer = Any order processing [OK]

Hint: Async means order can vary in processing [OK]

Common Mistakes:

• Assuming strict order always preserved
• Thinking reverse order is default
• Believing some messages get ignored

4. You have this Kafka consumer code snippet:

consumer.subscribe(['topic1'])
for message in consumer:
    print(message.value)
    consumer.commit()

What is the main issue that can cause scaling problems?

medium

A. Printing message values is not allowed in Kafka consumers.

B. Calling commit() inside the loop slows processing and blocks scaling.

C. Not subscribing to the topic correctly.

D. Using a for loop instead of while True.

Solution

1. Step 1: Identify commit() impact on performance

   Calling commit() after every message waits for confirmation, slowing down processing.

2. Step 2: Understand scaling impact

   This slows consumer throughput and limits how well the app can scale with many messages.

3. Final Answer:

   Calling commit() inside the loop slows processing and blocks scaling. -> Option B

4. Quick Check:

   Frequent commit() = Slow processing = Poor scaling [OK]

Hint: Avoid commit() inside message loop for better scaling [OK]

Common Mistakes:

• Thinking subscribe() is incorrect syntax
• Believing print() causes errors
• Confusing loop type with scaling issue

5. You want to design a scalable event-driven app using Kafka that handles thousands of users sending events simultaneously. Which approach best supports scaling?

hard

A. Send events directly between users without Kafka.

B. Use a single Kafka partition and one consumer to keep order.

C. Store all events in a database first, then process them sequentially.

D. Use multiple Kafka partitions and consumers to process events in parallel.

Solution

1. Step 1: Understand Kafka partitions and consumers

   Kafka partitions allow splitting event streams so multiple consumers can read in parallel.

2. Step 2: Connect parallel processing to scaling

   Using multiple partitions and consumers lets the app handle many events at once, improving scalability.

3. Final Answer:

   Use multiple Kafka partitions and consumers to process events in parallel. -> Option D

4. Quick Check:

   Partitions + consumers = Parallel processing = Scales well [OK]

Hint: Parallel consumers on partitions scale Kafka apps best [OK]

Common Mistakes:

• Choosing single partition limits throughput
• Processing events sequentially slows app
• Skipping Kafka loses event-driven benefits