Message broker architecture in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a message broker in simple terms?

A message broker is like a post office for software. It takes messages from one program and delivers them to another, helping them talk without knowing each other directly.

beginner

What role does Kafka play in message broker architecture?

Kafka acts as a fast and reliable message broker that stores and forwards messages between producers (senders) and consumers (receivers) in a way that can handle lots of data and many users.

beginner

Explain the concept of 'topics' in Kafka.

Topics are like mailboxes in Kafka. Producers send messages to a topic, and consumers read messages from that topic. Each topic holds messages about a specific subject.

beginner

What is the difference between a producer and a consumer in Kafka?

A producer is a program that sends messages to Kafka topics. A consumer is a program that reads messages from those topics. They work together but do different jobs.

intermediate

Why is Kafka considered scalable and fault-tolerant?

Kafka splits topics into partitions that can be spread across many servers. This lets it handle more messages and keep working even if some servers fail, making it scalable and reliable.

In Kafka, what is a 'topic'?

A A category or feed name to which messages are published

B A user who sends messages

C A server that stores messages

D A type of message format

A topic is a named stream of messages in Kafka where producers send data and consumers read from.

Who sends messages to Kafka topics?

A Consumers

B Brokers

C Producers

D Partitions

Producers are the programs or services that send messages to Kafka topics.

What makes Kafka fault-tolerant?

A Replicating partitions across multiple servers

B Storing messages in memory only

C Using a single server

D Deleting messages after reading

Kafka replicates partitions on multiple servers so if one fails, others can continue serving data.

What is a partition in Kafka?

A A type of message

B A division of a topic to spread load

C A consumer group

D A message format

Partitions split a topic into parts that can be stored on different servers to improve performance and scalability.

Which component reads messages from Kafka topics?

A Producer

B Partition

C Broker

D Consumer

Consumers are the programs that read messages from Kafka topics.

Describe the main components of Kafka's message broker architecture and how they interact.

Think about who sends messages, where messages go, how they are stored, and who reads them.

Explain why Kafka is suitable for handling large-scale data streams and how it ensures reliability.

Consider how Kafka spreads data and protects it from server failures.

Practice

1. What is the main role of a message broker like Kafka in an application?

easy

A. To create user interfaces for applications

B. To send messages between different parts of an application reliably

C. To run complex calculations on data

D. To store large files permanently

Solution

1. Step 1: Understand the purpose of a message broker

   A message broker helps different parts of an app communicate by sending messages.

2. Step 2: Identify Kafka's role

   Kafka acts as a reliable middleman to send and store messages in order.

3. Final Answer:

   To send messages between different parts of an application reliably -> Option B

4. Quick Check:

   Message broker = reliable message passing [OK]

Hint: Message brokers connect apps by passing messages [OK]

Common Mistakes:

• Thinking Kafka stores files permanently
• Confusing message brokers with UI tools
• Assuming Kafka does data calculations

2. Which of the following is the correct way to describe a Kafka topic?

easy

A. A user who sends messages to Kafka

B. A tool to monitor Kafka servers

C. A place where messages are stored and organized in order

D. A database table for storing user data

Solution

1. Step 1: Define what a Kafka topic is

   A Kafka topic is a category or feed name where messages are stored in order.

2. Step 2: Match the correct description

   Only A place where messages are stored and organized in order correctly describes a topic as a storage place for ordered messages.

3. Final Answer:

   A place where messages are stored and organized in order -> Option C

4. Quick Check:

   Kafka topic = ordered message storage [OK]

Hint: Topic = ordered message storage in Kafka [OK]

Common Mistakes:

• Confusing topic with user or tool
• Thinking topic is a database table
• Mixing topic with monitoring tools

3. Given this Kafka setup: Producer sends messages to topic orders. Consumer reads from orders. What will the consumer receive if the producer sends messages ["order1", "order2"] in order?

medium

A. ["order1", "order2"]

B. No messages because consumer reads from a different topic

C. ["order2", "order1"]

D. An error because messages are unordered

Solution

1. Step 1: Understand message order in Kafka topics

   Kafka keeps messages in the order they are sent within a topic.

2. Step 2: Trace the messages sent and received

   Producer sends ["order1", "order2"] to topic orders. Consumer reads from the same topic, so it receives messages in the same order.

3. Final Answer:

   ["order1", "order2"] -> Option A

4. Quick Check:

   Kafka preserves message order = ["order1", "order2"] [OK]

Hint: Kafka keeps message order per topic [OK]

Common Mistakes:

• Assuming messages arrive reversed
• Thinking consumer reads from different topic
• Believing Kafka does not guarantee order

4. You wrote code where a Kafka consumer tries to read from a topic but gets no messages. What is a likely cause?

medium

A. The consumer is subscribed to the wrong topic name

B. Kafka does not support consumers

C. Messages are deleted immediately after sending

D. Producer sends messages in the wrong format

Solution

1. Step 1: Check consumer subscription

   If the consumer subscribes to a wrong or misspelled topic, it won't receive messages.

2. Step 2: Evaluate other options

   Kafka supports consumers, messages are not deleted immediately, and format issues usually cause errors, not empty reads.

3. Final Answer:

   The consumer is subscribed to the wrong topic name -> Option A

4. Quick Check:

   Wrong topic subscription = no messages [OK]

Hint: Check topic name spelling for consumer subscription [OK]

Common Mistakes:

• Assuming Kafka lacks consumer support
• Thinking messages vanish instantly
• Blaming message format without error

5. You want to ensure messages sent to Kafka are not lost even if a server crashes. Which Kafka feature helps achieve this?

hard

A. Sending messages without keys

B. Using a single broker to simplify management

C. Deleting messages immediately after consumption

D. Replication of topic partitions across multiple brokers

Solution

1. Step 1: Understand message durability in Kafka

   Kafka replicates partitions of topics across multiple brokers to avoid data loss if one fails.

2. Step 2: Evaluate options for reliability

   Single broker risks data loss, deleting messages early loses data, and keys don't affect durability.

3. Final Answer:

   Replication of topic partitions across multiple brokers -> Option D

4. Quick Check:

   Replication = message safety on server crash [OK]

Hint: Use replication to keep messages safe [OK]

Common Mistakes:

• Thinking single broker is safer
• Deleting messages early to save space
• Ignoring replication importance