advancedKubernetes Deployment

Why does scaling a Kafka consumer's Kubernetes Deployment beyond the topic's partition count not improve throughput?

Kafka assigns each partition to exactly one consumer within a consumer group at a time — if you have more pod replicas than partitions, the extra pods simply sit idle with no partitions assigned, since a single partition cannot be split across two consumers in the same group.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full Spring Ecosystem Mastery library.

Why does scaling a Kafka consumer's Kubernetes Deployment beyond the topic's partition count not improve throughput?

Next Step

Continue to What Kubernetes concept maps naturally onto 'a consumer instance that needs a stable identity across restarts', and why might that matter for Kafka?← Back to all Kafka & Microservices questions