Why Kafka exists - Why It Works

Introduction

Kafka exists to help different parts of a system talk to each other by sending messages quickly and reliably. It solves the problem of moving data between apps without losing it or slowing down the system.

When you want to collect data from many sources and process it later without losing any messages

When you need to connect different apps so they can work together by sharing information instantly

When you want to handle a large stream of events, like user clicks or sensor data, in real time

When you want to build a system that keeps working even if some parts fail temporarily

When you want to store messages safely so they can be read multiple times or by many apps

Commands

This command creates a new topic named 'example-topic' with 3 partitions to allow parallel processing and a replication factor of 1 for data safety.

Terminal

kafka-topics.sh --create --topic example-topic --bootstrap-server localhost:9092 --partitions 3 --replication-factor 1

Expected Output

Created topic example-topic.

→

--topic - Name of the topic to create

→

--partitions - Number of partitions for parallelism

→

--replication-factor - Number of copies of data for fault tolerance

This command starts a simple producer that sends messages to the 'example-topic'. You can type messages and press enter to send them.

Terminal

kafka-console-producer.sh --topic example-topic --bootstrap-server localhost:9092

Expected Output

No output (command runs silently)

→

--topic - Topic to send messages to

→

--bootstrap-server - Kafka server address

This command starts a consumer that reads all messages from the beginning of 'example-topic', showing how Kafka stores messages for later use.

Terminal

kafka-console-consumer.sh --topic example-topic --bootstrap-server localhost:9092 --from-beginning

Expected Output

Hello

World

Kafka is great

→

--topic - Topic to read messages from

→

--from-beginning - Read all messages from the start

Key Concept

If you remember nothing else, remember: Kafka exists to move data between apps quickly, safely, and without losing messages.

Common Mistakes

Creating a topic without enough partitions

This limits how many consumers can read in parallel, slowing down processing.

Create topics with multiple partitions to allow parallel processing.

Not setting replication factor

Without replication, data can be lost if a server fails.

Set replication factor to at least 2 for data safety.

Starting consumer without --from-beginning when you want all messages

The consumer will only see new messages, missing old ones.

Use --from-beginning to read all messages from the start.

Summary

Kafka helps apps send and receive messages quickly and safely.

Create topics with partitions and replication for performance and safety.

Use producers to send messages and consumers to read them, optionally from the start.

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