파티션 및 오프셋 이해

Imagine a Kafka topic as a category for messages. To handle lots of messages efficiently, Kafka divides a topic into smaller, ordered segments called partitions.

Think of each partition as its own mini-log. Messages are appended to the end of a partition in the order they arrive. Once written, messages in a partition are immutable.

It's crucial to understand that while messages within a single partition are strictly ordered, there's no guaranteed order across different partitions of the same topic.

• Ordered: Messages in one partition always have a clear sequence.
• Immutable: Once a message is written to a partition, it cannot be changed.
• Append-only: New messages are always added to the end.

Partitions are the backbone of Kafka's scalability and parallelism. Here's why they matter:

• Parallel Processing: Multiple consumers can read from different partitions of the same topic simultaneously.
• Distributed Storage: Partitions can be spread across different Kafka brokers (servers) in a cluster. This allows topics to handle more data than a single server could.

When a producer sends a message, Kafka needs to decide which partition it should go into. This is called partitioning strategy:

• With a Key: If a message includes a key (e.g., a user ID), Kafka uses a hash of that key to consistently assign it to the same partition. This ensures all messages for a specific key are processed in order.
• Without a Key: If no key is provided, Kafka typically uses a round-robin approach, distributing messages evenly across all partitions.

This Java example shows how a producer sends messages to a topic, explicitly providing a key. Messages with the same key will end up in the same partition.

Every message within a Kafka partition has a unique, sequential identifier called an offset. Think of it as an index number for messages within that specific partition.

• The first message in a partition has offset 0.
• The next message has offset 1, and so on.
• Offsets are local to each partition.

Offsets are critical for consumers to track their progress. A consumer keeps a record of the offset of the last message it successfully processed in each partition.

This allows consumers to:

• Resume processing exactly where they left off if they stop or crash.
• Know which messages they still need to read.

After processing messages, consumers need to inform Kafka about their progress by committing their offsets. This means saving the current offset to a special Kafka topic (__consumer_offsets).

Committing can be:

• Automatic: Kafka commits offsets periodically in the background.
• Manual: The application explicitly tells Kafka when to commit offsets, offering more control over processing guarantees.

Let's test your knowledge about Kafka partitions and offsets.

Today, we explored two core Kafka concepts:

• Partitions: These segments divide a topic, enabling parallel processing, distributed storage, and ordered messages within each partition.
• Offsets: These sequential IDs track the position of messages within a partition, allowing consumers to precisely manage their progress and resume reliably.

Understanding these concepts is key to building scalable and robust Kafka applications!