[Verse 1]
ZooKeeper's been our metadata friend
But dependencies we need to end
KIP-500 shows a better way
Self-managed quorum saves the day
Controllers form their own consensus
Raft protocol keeps things defenseless
[Chorus]
KRaft mode, no Zoo needed
Quorum-based, self-completed
Metadata logs in perfect sync
Controllers vote without a blink
KRaft mode, streamlined and clean
Best architecture we've ever seen
[Verse 2]
Check the docs on Apache's site
KRaft section makes it crystal bright
Configuration starts with process roles
Controller, broker, or combined goals
Set your quorum voters carefully
Three or five nodes work perfectly
[Chorus]
KRaft mode, no Zoo needed
Quorum-based, self-completed
Metadata logs in perfect sync
Controllers vote without a blink
KRaft mode, streamlined and clean
Best architecture we've ever seen
[Bridge]
KIP-631 defines the controller
Quorum-based, it's so much smaller
Leader election through Raft consensus
Metadata partitions, zero expenses
Read the documentation thoroughly
Every detail matters, you will see
[Verse 3]
Bootstrap servers point to controllers
Cluster metadata, they're the providers
Log directories need proper planning
Controller logs need understanding
Official docs have all the answers
Migration guides for all advancers
[Chorus]
KRaft mode, no Zoo needed
Quorum-based, self-completed
Metadata logs in perfect sync
Controllers vote without a blink
KRaft mode, streamlined and clean
Best architecture we've ever seen
[Outro]
When you're ready to deploy KRaft
Read the docs, both fore and aft
Apache Kafka's future's bright
KRaft mode makes everything right