[Verse 1] ZooKeeper's reign is ending now A quorum built from Kafka's own Controllers cluster, take a bow Event streams carved in metadata stone No external keeper anymore The protocol lives within the core [Chorus] KRaft means Kafka Raft inside Eating dogfood with controller pride Metadata flows like events should be Consensus native, finally free KRaft, KRaft, the future's here ZooKeeper fades, the path is clear [Verse 2] Three controllers form the quorum base Event logs hold the cluster state Each decision leaves a metadata trace No more external keeper's weight The architecture speaks in streams Events and consensus share the same dreams [Chorus] KRaft means Kafka Raft inside Eating dogfood with controller pride Metadata flows like events should be Consensus native, finally free KRaft, KRaft, the future's here ZooKeeper fades, the path is clear [Bridge] From ensemble to controller nodes The paradigm completely shifts Event-based consensus explodes Through streams where metadata drifts KIP five hundred leads the charge Making Kafka's footprint less large [Verse 3] Controllers vote on every change Event sourcing tells the tale No coordination that's strange Built-in Raft will never fail Simplified deployment waits While event logs coordinate [Chorus] KRaft means Kafka Raft inside Eating dogfood with controller pride Metadata flows like events should be Consensus native, finally free KRaft, KRaft, the future's here ZooKeeper fades, the path is clear [Outro] Event-driven all the way Metadata streams and controllers play KRaft consensus, here to stay
← 1 Why KRaft Exists | 3 The Raft Consensus Protocol Primer →