Message key and value in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the message key in Kafka?

The message key is used to determine the partition where the message will be stored. It helps in ordering messages with the same key and enables message grouping.

beginner

What does the message value represent in Kafka?

The message value contains the actual data or payload that you want to send to Kafka consumers.

intermediate

How does Kafka use the message key to maintain order?

Kafka ensures that all messages with the same key go to the same partition, so their order is preserved within that partition.

intermediate

Can a Kafka message have a null key? What does it mean?

Yes, a Kafka message can have a null key. This means the message will be distributed to partitions in a round-robin or random manner, without key-based ordering.

intermediate

Why is it important to choose a good message key?

Choosing a good message key helps balance load across partitions and ensures related messages are processed in order, improving performance and consistency.

What does the message key in Kafka determine?

A The partition where the message is stored

B The size of the message

C The timestamp of the message

D The consumer group

The message key is used to decide which partition the message will be sent to.

What happens if a Kafka message has a null key?

A It is sent to a random partition

B It is rejected by Kafka

C It is sent to all partitions

D It is stored in a special partition

Messages with null keys are distributed across partitions randomly or round-robin.

Which part of a Kafka message contains the actual data?

A Message key

B Message value

C Partition ID

D Offset

The message value holds the actual payload or data sent to consumers.

Why is ordering guaranteed for messages with the same key?

A Because keys are unique

B Because Kafka sorts messages by timestamp

C Because they go to the same partition

D Because consumers reorder messages

Messages with the same key are sent to the same partition, preserving their order.

What is a benefit of choosing a good message key?

A Automatic message encryption

B Faster message compression

C Larger message size

D Better load balancing and message ordering

A good key helps balance load and keeps related messages ordered.

Explain how Kafka uses the message key to manage message distribution and ordering.

Think about how messages with the same key are grouped.

Describe the difference between message key and message value in Kafka messages.

One decides where the message goes, the other is the actual data.

Practice

1. What is the primary role of the message key in Kafka?

easy

A. To decide which partition the message goes to

B. To store the actual data of the message

C. To encrypt the message content

D. To delete old messages automatically

Solution

1. Step 1: Understand message key purpose

   The message key in Kafka is used to determine the partition where the message will be stored.

2. Step 2: Differentiate key and value roles

   The message value holds the actual data, while the key helps with partitioning and ordering.

3. Final Answer:

   To decide which partition the message goes to -> Option A

4. Quick Check:

   Message key = Partition decision [OK]

Hint: Key decides partition, value holds data [OK]

Common Mistakes:

• Confusing key with message value
• Thinking key encrypts data
• Assuming key deletes messages

2. Which of the following is the correct way to send a Kafka message with a key and value in Java?

easy

A. producer.send(new ProducerRecord<>("topic", value));

B. producer.send(new ProducerRecord<>(key, value));

C. producer.send("topic", value);

D. producer.send(new ProducerRecord<>("topic", key, value));

Solution

1. Step 1: Review ProducerRecord constructor

   The correct constructor for sending a message with key and value includes topic, key, and value in that order.

2. Step 2: Check each option

   producer.send(new ProducerRecord<>("topic", key, value)); uses new ProducerRecord<>("topic", key, value), which is correct syntax. Others miss topic or key.

3. Final Answer:

   producer.send(new ProducerRecord<>("topic", key, value)); -> Option D

4. Quick Check:

   ProducerRecord(topic, key, value) = correct [OK]

Hint: ProducerRecord needs topic, key, then value [OK]

Common Mistakes:

• Omitting the topic parameter
• Swapping key and value order
• Using wrong constructor overload

3. Given the following Kafka producer code snippet, what will be the key of the message sent?

ProducerRecord record = new ProducerRecord<>("orders", "12345", "order details");
producer.send(record);

medium

A. "orders"

B. null

C. "12345"

D. "order details"

Solution

1. Step 1: Identify parameters in ProducerRecord

   The constructor is ProducerRecord(topic, key, value). Here, "orders" is topic, "12345" is key, and "order details" is value.

2. Step 2: Determine the key value

   The key is the second argument, which is "12345".

3. Final Answer:

   "12345" -> Option C

4. Quick Check:

   Second argument = key = "12345" [OK]

Hint: Second argument in ProducerRecord is key [OK]

Common Mistakes:

• Confusing topic with key
• Choosing message value as key
• Assuming key is null if not obvious

4. Identify the error in this Kafka producer code snippet:

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

medium

A. Message key cannot be null

B. This code is valid; no error

C. ProducerRecord constructor parameters are in wrong order

D. Message value cannot be null

Solution

1. Step 1: Check if null key is allowed

   Kafka allows message keys to be null; this means messages can be sent without a key.

2. Step 2: Verify constructor usage

   The constructor ProducerRecord<>("topic", null, "data") is valid and sends a message with no key.

3. Final Answer:

   This code is valid; no error -> Option B

4. Quick Check:

   Null key allowed in Kafka messages [OK]

Hint: Null keys are allowed in Kafka messages [OK]

Common Mistakes:

• Assuming key must never be null
• Confusing parameter order
• Thinking value cannot be null without checking

5. You want to ensure all messages with the same user ID go to the same partition for ordering. Which Kafka message feature should you use and how?

hard

A. Use the user ID as the message key to ensure partitioning by key

B. Include the user ID only in the message value and leave key null

C. Set the user ID as the topic name

D. Send messages without keys and rely on default partitioning

Solution

1. Step 1: Understand partitioning by key

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

2. Step 2: Apply to user ID scenario

   Using the user ID as the message key ensures all messages for that user go to the same partition, preserving order.

3. Final Answer:

   Use the user ID as the message key to ensure partitioning by key -> Option A

4. Quick Check:

   Key = user ID for partitioning [OK]

Hint: Use key for grouping messages by user ID [OK]

Common Mistakes:

• Putting user ID only in value loses partition control
• Changing topic per user is inefficient
• Relying on default partitioning breaks ordering