liveBook · Manning

KRaft

KRaft is Apache Kafka’s Raft-based metadata-management mode, using an internal controller quorum instead of ZooKeeper.

How 2 Manning books explain it

Kafka for Architects

KRaft is Kafka's metadata management mode that uses an internal controller quorum instead of ZooKeeper.

How it is used
Positions KRaft as Kafka’s internal metadata and coordination mode when planning a cluster for production.
How deep it goes
Explains controller roles, metadata-log replication, majority commits, and failure handling, but defers step-by-step configuration.
Examples
Illustrates majority commit with a metadata-update diagram and quorum loss with a data-center outage scenario.
What you can do after
Evaluate/understand controller placement, quorum-loss consequences, and the migration implications of removing ZooKeeper.

Read how Kafka for Architects explains KRaft →

Apache Kafka in Action

KRaft is Kafka's protocol for managing cluster metadata and internal coordination without an external coordination system.

How it is used
Coordinates Kafka cluster metadata, controller election, partition assignments, and leader changes without a separate ZooKeeper service.
How deep it goes
Explains controller roles, failure tolerance, metadata storage, and migration steps, but does not detail Raft’s consensus algorithm.
Examples
Uses bank-transfer partitions and one-, three-, and five-controller configurations to illustrate coordination and failure tolerance.
What you can do after
Operate/configure it by choosing controller capacity and planning a verified migration from ZooKeeper-backed coordination.

Read how Apache Kafka in Action explains KRaft →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.