3 ms·
i'm having a hard time understanding what scenario requires a queue semantic instead of a stream one. Is is the ability to parallelize consuming to a super lar
by bsaul 3y ago
i'm having a hard time understanding what scenario requires a queue semantic instead of a stream one.
Is is the ability to parallelize consuming to a super large amount, without having to setup partitions ?
I'm planning on using kafka for a job queue, and i like the idea that i can add ordering definition if i need to, and that i can keep the jobs in the queue for auditing later on if i need to. What am i missing ?
- Spivak 3y ago> without having to setup partitions Without being limited by partitions. In Kafka your unit of parallelism is partitions but what happens when you don't care at all (or much) about ordering and just want to add or remove consumers to match your current load? Queue semantics. In Kafka the number of partitions can go up, but not down. And even when you do that the messages don't get split up to fill the new partition so you can't burn down a backup by adding more partitions or more consumers -- ope.