Skip to main content
PreparationZone Logo
PrepZone

Consumer Groups and Partition Assignment

One consumer per partition per group — how VaultCommerce inventory and payment services scale independently.

Pass checkpoint below

Why this matters

  • VaultCommerce inventory-service and email-service are separate groups on the same topic — both receive every order.
  • Scaling consumers beyond partition count wastes pods — VaultCommerce HPA caps at partition count.
  • group.id is the offset namespace — resetting it rewinds consumption.
  • Core concept for every consumer article and ops playbook.
Topic partitions
P0
P1
P2
Group: inventory-service
Consumer Areads P0
Consumer Breads P1
Consumer Creads P2
Each partition is consumed by exactly one consumer in the group. Add consumers up to partition count.

Partition assignment

Group coordinator broker tracks members and triggers rebalance on join/leave. Range assignor (default) can imbalance; VaultCommerce uses CooperativeStickyAssignor for incremental rebalances. 12 partitions, 4 inventory consumers → 3 partitions each.

Key points

  • group.id — logical consumer set name; offset commits are per group-topic-partition
  • Group coordinator — broker managing membership and offset commits
  • Partition assignment — one consumer per partition within a group
  • Static membership — group.instance.id reduces rebalance on rolling deploys
  • Multiple groups — fan-out without duplicate assignment within a group

The rest of this guide is part of Pro

Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.

Still to come · 2 sections

  • Independent groups on one topic
  • VaultCommerce rollout checklist

Test yourself

Answer these before moving on — recall is what makes it stick.