<p>Imagine a scenario in which a producer is producing 100 messages per second, and we're working on a system that consuming messages ASAP matters a lot, even 5 seconds delay might result in a decision not to take care of that message anymore. also, the order of messages does not matter.</p>
<p>So I don't want to use a basic queue and a single pod listening on a single partition to consume messages, since in order to consume a message, the consumer needs to make multiple remote API calls and this might take time.</p>
<p>In such a scenario, I'm thinking of a single Kafka topic, with 100 partitions. and for each partition, I'm gonna have a separate machine (pod) listening for partitions 0 to 99.</p>
<p>Am I thinking right? this is my first project with Kafka. this seems a little weird to me.</p>

behz4d
<p>Your bottleneck is your application processing the event, not Kafka.
when you have ten consumers, there is overhead for connecting each consumer to Kafka so it will lower the performance.
I advise focusing on your application performance rather than message broker.</p>
<p>Kafka p99 Latency is 5 ms with 200 MB/s load.</p>
<p><a href="https://developer.confluent.io/learn/kafka-performance/" rel="nofollow noreferrer">https://developer.confluent.io/learn/kafka-performance/</a></p>
