Skip to main content
PreparationZone Logo
PrepZone

KRaft: Kafka Without ZooKeeper

Modern Kafka runs metadata in KRaft quorum — faster failover, simpler ops, and the only path forward on Kafka 4.x.

Pass checkpoint below

Why this matters

  • VaultCommerce migrated from ZooKeeper to KRaft in 2025 — failover dropped from ~15s to under 5s.
  • Kafka 4.x removes ZooKeeper entirely; KRaft is the only supported metadata mode going forward.
  • Simpler ops: one fewer system to patch, monitor, and secure.
  • Interviewers now expect KRaft architecture, not ZK-based explanations.
KRaft controllers
Controller 1
Controller 2
Controller 3
Data brokers
Broker 1Partitions
Broker 2Partitions
Broker 3Partitions
Controller quorum stores cluster metadata. Brokers handle data partitions — no ZooKeeper required.

Controllers and metadata log

A subset of brokers (or dedicated nodes) run as KRaft controllers. They replicate metadata records — topic configs, partition assignments, broker registrations — via Raft. On broker startup, it reads the metadata log to know which partitions to host. VaultCommerce runs 3 controllers (odd quorum) across AZs.

Key points

  • KRaft quorum — odd number of controller nodes (typically 3 or 5) for Raft consensus
  • Metadata log — internal topic storing cluster topology changes
  • Controller leader — single active controller handling metadata mutations
  • Combined mode — broker and controller on same node (dev/small prod)
  • Dedicated controllers — separate JVMs for large clusters (VaultCommerce at 6+ brokers)

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

  • Migration and compatibility
  • VaultCommerce rollout checklist

Test yourself

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