[Verse 1] In the world of KRaft there's a choice to make Three different roles for your cluster's sake Controller nodes keep the metadata straight While broker nodes handle client requests all day [Chorus] Controller, broker, or combined together Choose your roles like choosing the weather Process dot roles equals your decision Controller, broker, perfect division Size your cluster, pick your topology KRaft node roles, that's the key [Verse 2] Set process roles to controller alone Metadata quorum is their only zone They manage the state but don't serve requests Keeping cluster information at its best [Chorus] Controller, broker, or combined together Choose your roles like choosing the weather Process dot roles equals your decision Controller, broker, perfect division Size your cluster, pick your topology KRaft node roles, that's the key [Verse 3] Broker nodes serve your produce and consume Client connections fill up the room Set process roles to broker they'll be Handling data flows efficiently [Bridge] Combined nodes do it all in one Broker comma controller, two roles as one Single JVM runs them both Perfect for dev or when cluster growth Is small and simple, resources tight Combined topology feels just right [Chorus] Controller, broker, or combined together Choose your roles like choosing the weather Process dot roles equals your decision Controller, broker, perfect division Size your cluster, pick your topology KRaft node roles, that's the key [Outro] Deployment size will guide your way Large clusters separate roles today Small setups can combine with ease KRaft node roles bring you peace
← 3 The Raft Consensus Protocol Primer | 1 The KRaft Protocol (Raft Implementation) →