3 ms·
A Kafka topic is more synonymous with a "message queue" and a partition is a division among hardware for parallelism. So you can have one topic, partitioned to
by squeaky-clean 9y ago
A Kafka topic is more synonymous with a "message queue" and a partition is a division among hardware for parallelism.
So you can have one topic, partitioned to 5 consumers, and each consumer storing the received events. Each consumer will see their own messages in-order, but if you merge the 5 it is not guaranteed to be ordered.
I'd guess this is what RocketMQ means by "scale out gracefully"
- nicktelford 9y agoIn Kafka, multiple consumers can recieve multiple partitions. The only thing, from a consumer's perspective, that's special about partitions is that it's the level at which message ordering is guaranteed. That's exactly the same semantics provided by RocketMQ's "message queues", from what I can tell - except perhaps that these message queues are explicitly subscribed to? If that's the case, you can do that in Kafka too, but it's generally discouraged, as it can lead to performance problems.