Why Kafka exists - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why was Kafka created?

Kafka was created to solve which main problem in data systems?

A To provide a distributed messaging system that can handle high throughput and fault tolerance

B To replace traditional relational databases with a new query language

C To create a user interface for managing cloud resources

D To serve as a web server for hosting websites

💡 Hint

Think about what kind of data flow Kafka is designed to support.

Kafka was designed as a distributed messaging system to handle large volumes of data with high speed and reliability.

❓ Predict Output

intermediate

Kafka Producer Message Delivery

What will be the output when a Kafka producer sends a message with acks=all?

Kafka

producer.send('topic1', b'message').get()  # with acks='all'

A The producer waits for all replicas to acknowledge before confirming the send

B The producer sends the message without waiting for any acknowledgment

C The producer retries sending the message indefinitely without acknowledgment

D The producer waits only for the leader broker to acknowledge

💡 Hint

Consider what acks=all means for message durability.

Setting acks=all means the producer waits for all in-sync replicas to confirm the message, ensuring durability.

❓ Predict Output

advanced

Kafka Consumer Offset Behavior

What happens if a Kafka consumer commits an offset that is higher than the last message in the partition?

Kafka

consumer.commit(offset=1000)  # when last message offset is 900

A The consumer will throw an OffsetOutOfRangeException immediately

B The consumer will read messages starting from offset 900 instead

C The consumer will reset to offset 0 automatically

D The consumer will start reading from offset 1000, which does not exist, causing it to wait for new messages

💡 Hint

Think about how Kafka handles offsets beyond the current log end.

If the committed offset is beyond the last message, the consumer waits for new messages at that offset.

🧠 Conceptual

advanced

Kafka's Role in Event-Driven Architectures

Why is Kafka often used as the backbone in event-driven architectures?

A Because it automatically generates user interfaces for events

B Because it stores data in relational tables for easy querying

C Because it provides a scalable, fault-tolerant, and durable event streaming platform

D Because it replaces all microservices with a single monolithic app

💡 Hint

Consider Kafka's strengths in handling streams of data reliably.

Kafka is used in event-driven systems because it can handle large streams of events reliably and scale easily.

🧠 Conceptual

expert

Kafka's Partitioning and Scalability

How does Kafka achieve horizontal scalability and parallel processing?

A By using a centralized database to manage all messages

B By dividing topics into partitions that can be distributed across multiple brokers

C By limiting the number of consumers to one per topic

D By storing all data in a single broker to avoid network overhead

💡 Hint

Think about how Kafka spreads workload to handle more data.

Kafka splits topics into partitions, allowing multiple brokers and consumers to work in parallel, increasing scalability.

Practice

1. Why does Kafka exist in software systems?

easy

A. To help programs send and receive messages reliably and quickly

B. To replace databases for storing user profiles

C. To create user interfaces for web applications

D. To compile code faster

Solution

1. Step 1: Understand Kafka's main purpose

   Kafka is designed to handle messaging between programs efficiently and reliably.

2. Step 2: Compare options with Kafka's role

   The other options describe unrelated tasks like databases, UI, or compiling, which Kafka does not do.

3. Final Answer:

   To help programs send and receive messages reliably and quickly -> Option A

4. Quick Check:

   Kafka = Reliable fast messaging [OK]

Hint: Kafka is about messaging, not databases or UI [OK]

Common Mistakes:

• Confusing Kafka with a database
• Thinking Kafka builds user interfaces
• Assuming Kafka compiles code

2. Which of the following is the correct way to describe Kafka's data storage?

easy

A. Kafka stores messages in tables like a database

B. Kafka stores messages in files on a user's desktop

C. Kafka stores messages only temporarily in memory

D. Kafka stores messages in topics for multiple programs to use

Solution

1. Step 1: Recall Kafka's storage method

   Kafka organizes messages into topics, which multiple programs can read from or write to.

2. Step 2: Evaluate each option

   Kafka stores messages in tables like a database is incorrect because Kafka does not use tables like a database. Kafka stores messages in files on a user's desktop is wrong because Kafka does not store messages on a user's desktop. Kafka stores messages only temporarily in memory is incorrect because Kafka stores messages durably, not just temporarily in memory.

3. Final Answer:

   Kafka stores messages in topics for multiple programs to use -> Option D

4. Quick Check:

   Kafka storage = Topics for sharing [OK]

Hint: Remember Kafka uses topics, not tables or temporary memory [OK]

Common Mistakes:

• Thinking Kafka stores data like a traditional database
• Assuming Kafka stores data only temporarily
• Confusing Kafka storage location with local files

3. Consider this scenario: A program sends messages to a Kafka topic, and multiple other programs read from it. What is the main benefit of this setup?

medium

A. Messages are lost if one program fails

B. Multiple programs can read the same messages independently

C. Only one program can read messages at a time

D. Messages are deleted immediately after being read

Solution

1. Step 1: Understand Kafka's message consumption model

   Kafka allows multiple programs to read the same messages independently from a topic.

2. Step 2: Analyze each option

   Messages are lost if one program fails is false because Kafka ensures message durability. Only one program can read messages at a time is incorrect because Kafka supports multiple consumers reading simultaneously. Messages are deleted immediately after being read is wrong because Kafka retains messages for a configured time, not deleting immediately after reading.

3. Final Answer:

   Multiple programs can read the same messages independently -> Option B

4. Quick Check:

   Kafka supports multiple independent readers [OK]

Hint: Kafka lets many programs read same messages independently [OK]

Common Mistakes:

• Believing messages disappear after one read
• Thinking only one consumer can read at a time
• Assuming message loss on failure

4. A developer wrote code to send messages to Kafka but notices messages are not received by consumers. What could be a likely error?

medium

A. Kafka does not support multiple consumers

B. Kafka deletes messages immediately after sending

C. The topic name used by producer and consumer do not match

D. Kafka requires messages to be sent as files

Solution

1. Step 1: Identify common communication errors in Kafka

   If producer and consumer use different topic names, messages won't be received.

2. Step 2: Evaluate other options

   Kafka does not support multiple consumers is false; Kafka supports multiple consumers. Kafka deletes messages immediately after sending is incorrect; Kafka retains messages for a set time. Kafka requires messages to be sent as files is wrong; Kafka messages are sent as data, not files.

3. Final Answer:

   The topic name used by producer and consumer do not match -> Option C

4. Quick Check:

   Matching topic names needed for communication [OK]

Hint: Check topic names match between sender and receiver [OK]

Common Mistakes:

• Assuming Kafka deletes messages immediately
• Thinking Kafka only supports one consumer
• Believing messages must be files

5. You want to build a real-time system where many services process the same data stream independently and reliably. Why is Kafka a good choice?

hard

A. Kafka allows multiple consumers to read the same data without losing messages

B. Kafka stores data only temporarily, so it is fast but unreliable

C. Kafka requires all consumers to read messages in order and together

D. Kafka is designed only for batch processing, not real-time data

Solution

1. Step 1: Understand Kafka's support for real-time data and multiple consumers

   Kafka stores messages durably and allows many consumers to read independently, making it reliable for real-time systems.

2. Step 2: Analyze incorrect options

   Kafka stores data only temporarily, so it is fast but unreliable is false because Kafka stores data durably, not just temporarily. Kafka requires all consumers to read messages in order and together is incorrect; consumers can read independently and at different speeds. Kafka is designed only for batch processing, not real-time data is wrong; Kafka is designed for real-time streaming, not just batch.

3. Final Answer:

   Kafka allows multiple consumers to read the same data without losing messages -> Option A

4. Quick Check:

   Kafka = Reliable real-time multi-consumer streaming [OK]

Hint: Kafka supports reliable real-time multi-reader streams [OK]

Common Mistakes:

• Thinking Kafka only supports batch processing
• Assuming Kafka loses messages quickly
• Believing consumers must read together