[Verse 1] There once was a time when Kafka relied On ZooKeeper standing by its side But scaling up meant complexity grew Metadata scattered, performance fell through Colin McCabe saw a better way KIP-500 would save the day [Chorus] KRaft mode, no more ZooKeeper pain Self-managing cluster, breaking the chain Raft protocol keeps consensus strong Leader election where it belongs KRaft mode, streamlined and clean The simplest Kafka you've ever seen [Verse 2] Jason showed us how Raft works inside One leader chosen, others subside Heartbeats flowing to stay alive If leader fails, new one will thrive Log replication keeps data safe Majority wins, no time to waste [Chorus] KRaft mode, no more ZooKeeper pain Self-managing cluster, breaking the chain Raft protocol keeps consensus strong Leader election where it belongs KRaft mode, streamlined and clean The simplest Kafka you've ever seen [Bridge] Confluent made it simple to see Fewer moving parts means stability Bootstrapping easier than before No external dependencies to store Metadata controllers lead the way Built into Kafka, here to stay [Verse 3] Three key players in this new design Controllers, brokers, working in line Event-driven architecture flows Self-contained system that truly knows How to manage its own state No ZooKeeper dependency weight [Chorus] KRaft mode, no more ZooKeeper pain Self-managing cluster, breaking the chain Raft protocol keeps consensus strong Leader election where it belongs KRaft mode, streamlined and clean The simplest Kafka you've ever seen [Outro] From KIP-500 to production use KRaft has set your clusters loose No more ZooKeeper in the way Welcome to Kafka's brighter day
← 3 Common Connector Patterns | 2 Strimzi MirrorMaker 2 Configuration →