Skip to content

Commit 475fe76

Browse files
committed
Improved README readability
1 parent 8657887 commit 475fe76

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Let's understand how this works with an example.
88

99
![Partitioner Overview](images/partitioner-overview.png)
1010

11-
Here we can see that the partitions were grouped into the buckets `Platinum` and `Gold`. The Platinum bucket has a higher priority and therefore was configured to have `70%` of the allocation, whereas the Gold bucket has lower priority and therefore was configured to have only `30%`. This means that for a topic that contains `6` partitions, `4` of them will be associated with the Platinum bucket and `2` will be associated with the Gold bucket. To implement the message prioritization, there has to be a process that ensures that messages with higher priority will end up in one the partitions from the Platinum bucket and messages with lower priority will end up in one the partitions from the Gold bucket. Consumers need to subscribe to the topic knowing which buckets they need to be associated with. This means that developers can decide to execute more consumers for the Platinum bucket and fewer consumers for the Gold bucket to ensure that they process high priority messages faster.
11+
Here we can see that the partitions were grouped into the buckets `Platinum` and `Gold`. The Platinum bucket has a higher priority and therefore was configured to have `70%` of the allocation, whereas the Gold bucket has lower priority and therefore was configured to have only `30%`. This means that for a topic that contains `6` partitions, `4` of them will be associated with the Platinum bucket and `2` will be associated with the Gold bucket. To implement the prioritization, there has to be a process that ensures that messages with higher priority will end up in one the partitions from the Platinum bucket and messages with lower priority will end up in one the partitions from the Gold bucket. Consumers need to subscribe to the topic knowing which buckets they need to be associated with. This means that developers can decide to execute more consumers for the Platinum bucket and fewer consumers for the Gold bucket to ensure that they process high priority messages faster.
1212

1313
To ensure that each message will end up in their respective bucket, use the `BucketPriorityPartitioner`. This partitioner uses data in the message key to decide which bucket to use and therefore which partition from the bucket the message should be written. This partitioner distributes the messages within the bucket using a round robin algorithm to maximize consumption parallelism. On the consumer side, use the `BucketPriorityAssignor` to ensure that the consumer will be assigned only to the partitions that represent the bucket they want to process.
1414

0 commit comments

Comments
 (0)