Why Partition concept in Kafka? - Purpose & Use Cases

The Big Idea

What if you could deliver thousands of messages at once without dropping any?

The Scenario

Imagine you have a huge stack of letters to deliver, but you try to carry them all in one bag and deliver them one by one.

This is like handling all messages in Kafka without partitions.

The Problem

Carrying all letters in one bag is slow and tiring.

Similarly, processing all messages in a single stream causes delays and risks losing messages if something breaks.

The Solution

Partitions split the big stack of letters into smaller bags, each handled separately.

This lets multiple delivery people work at the same time, making the process faster and safer.

Before vs After

✗ Before

topic = 'orders'
consumer = KafkaConsumer(topic)
for message in consumer:
    process(message)

✓ After

topic = 'orders'
consumer = KafkaConsumer(topic)
for message in consumer:
    process(message)
# Multiple consumers handle different partitions in parallel

What It Enables

Partitions let Kafka handle huge amounts of data quickly and reliably by dividing work across many workers.

Real Life Example

A big online store uses partitions to process thousands of orders at once, so customers get fast updates and smooth service.

Key Takeaways

Partitions split data into smaller parts for easier handling.

This allows parallel processing and better speed.

It improves reliability and scalability in message systems.

Practice

1.

What is the main purpose of partitions in a Kafka topic?

easy

A. To split the topic into smaller parts for better speed and order

B. To encrypt messages for security

C. To store messages permanently on disk

D. To compress messages to save space

Solution

1. Step 1: Understand the role of partitions in Kafka

   Partitions divide a topic into smaller parts to allow parallel processing and maintain message order within each partition.

2. Step 2: Identify the main benefit of partitions

   Partitions improve speed by enabling parallelism and keep order for messages with the same key.

3. Final Answer:

   To split the topic into smaller parts for better speed and order -> Option A

4. Quick Check:

   Partitions = speed and order [OK]

Hint: Partitions split topics to speed up and keep order [OK]

Common Mistakes:

• Confusing partitions with encryption
• Thinking partitions store messages permanently
• Assuming partitions compress data

2.

Which of the following is the correct way to specify the number of partitions when creating a Kafka topic using the command line?

kafka-topics.sh --create --topic my-topic --bootstrap-server localhost:9092 --partitions ?

easy

A. --num-partitions 3

B. --partition-count 3

C. --partitions 3

D. --partition 3

Solution

1. Step 1: Recall Kafka topic creation syntax

   The correct option to specify partitions is '--partitions' followed by the number.

2. Step 2: Match the correct option

   Among the options, '--partitions 3' is the valid syntax for setting 3 partitions.

3. Final Answer:

   --partitions 3 -> Option C

4. Quick Check:

   Partitions flag = --partitions [OK]

Hint: Use --partitions to set number when creating topic [OK]

Common Mistakes:

• Using --partition-count instead of --partitions
• Using --num-partitions which is invalid
• Using singular --partition flag

3.

Given a Kafka topic with 3 partitions, if messages with keys "key1", "key2", and "key1" are sent in that order, which partition will the second "key1" message go to?

medium

A. Partition 1

B. Same partition as the first "key1" message

C. Partition 0

D. A random partition different from the first "key1" message

Solution

1. Step 1: Understand key-based partitioning

   Kafka uses the message key to decide the partition. Messages with the same key always go to the same partition.

2. Step 2: Apply to the given keys

   Since both messages have key "key1", the second message will go to the same partition as the first "key1" message.

3. Final Answer:

   Same partition as the first "key1" message -> Option B

4. Quick Check:

   Same key = same partition [OK]

Hint: Same keys always go to the same partition [OK]

Common Mistakes:

• Assuming keys distribute randomly each time
• Thinking second message goes to a different partition
• Ignoring key-based partitioning

4.

Consider this Kafka producer code snippet in Java:

ProducerRecord record = new ProducerRecord<>("my-topic", null, "message");
producer.send(record);

What is the issue related to partitioning in this code?

medium

A. The key is null, so messages may be sent to random partitions

B. The topic name is missing

C. The message value is null

D. Producer is not closed after sending

Solution

1. Step 1: Analyze the ProducerRecord parameters

   The key parameter is null, which means Kafka cannot use key-based partitioning.

2. Step 2: Understand partition assignment without a key

   Without a key, Kafka assigns messages to partitions in a round-robin or default way, which can be random.

3. Final Answer:

   The key is null, so messages may be sent to random partitions -> Option A

4. Quick Check:

   Null key = random partition [OK]

Hint: Null key means no fixed partition, messages spread randomly [OK]

Common Mistakes:

• Thinking topic name is missing (it is present)
• Assuming message value is null (it's "message")
• Ignoring partitioning effect of null key

5.

You have a Kafka topic with 4 partitions. You want to ensure that all messages with the same customer ID go to the same partition to keep their order. Which approach should you use?

hard

A. Create 4 separate topics, one per customer

B. Send all messages to partition 0 manually

C. Use a random key for each message

D. Use the customer ID as the message key when producing messages

Solution

1. Step 1: Understand how Kafka assigns partitions

   Kafka uses the message key to decide which partition a message goes to, ensuring order for messages with the same key.

2. Step 2: Apply to customer ID ordering requirement

   Using the customer ID as the key ensures all messages for that customer go to the same partition and keep order.

3. Step 3: Evaluate other options

   Sending all to partition 0 limits scalability; random keys break order; separate topics complicate management.

4. Final Answer:

   Use the customer ID as the message key when producing messages -> Option D

5. Quick Check:

   Key = customer ID for order [OK]

Hint: Use customer ID as key to keep order in one partition [OK]

Common Mistakes:

• Sending all messages to one partition reduces scalability
• Using random keys breaks message order
• Creating multiple topics is unnecessary and complex