Why Kafka exists - The Real Reasons

The Big Idea

What if your apps could talk to each other without getting tangled in a mess of connections?

The Scenario

Imagine you have many different apps and services that need to talk to each other, sharing data like messages or events. You try to connect each one directly to every other one, like a big web of phone calls. It quickly becomes confusing and hard to manage.

The Problem

Manually connecting each service to every other service is slow and messy. If one service goes down, messages get lost. It's hard to keep track of what was sent or received. Scaling up means even more tangled connections and mistakes.

The Solution

Kafka acts like a central post office for messages. All services send their messages to Kafka, and others pick up what they need. This keeps communication organized, reliable, and fast, even when many services talk at once.

Before vs After

✗ Before

serviceA.sendTo(serviceB, message)
serviceA.sendTo(serviceC, message)
serviceB.sendTo(serviceC, message)

✓ After

kafka.publish('topic', message)
serviceB.subscribe('topic')
serviceC.subscribe('topic')

What It Enables

Kafka makes it easy to build systems where many parts share data smoothly, reliably, and at high speed.

Real Life Example

Think of a shopping website where orders, payments, and shipping all need to work together. Kafka helps these parts share updates instantly without losing any information.

Key Takeaways

Direct connections between many services get complicated fast.

Manual message passing is error-prone and hard to scale.

Kafka centralizes communication, making it reliable and easy to manage.

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