[Verse 1] In the Kafka world we need to share Multiple tenants everywhere Namespace walls keep data clean Isolation strategies unseen Dev and prod must stay apart Resource boundaries from the start [Chorus] Multi-tenant, keep it separate Quotas guard what we don't waste Name your topics, set your ACLs Shared or dedicated, choose it well Multi-tenant, scaling right Kubernetes keeps it all in sight [Verse 2] Produce and consume byte rates controlled Request quotas, stories told Throttling kicks when limits breach Performance lessons that we teach User principals get their slice Resource management, roll the dice [Chorus] Multi-tenant, keep it separate Quotas guard what we don't waste Name your topics, set your ACLs Shared or dedicated, choose it well Multi-tenant, scaling right Kubernetes keeps it all in sight [Verse 3] Topic naming with a plan Team prefix, understand the span Environment tags make it clear Which data belongs to whom here ACL patterns lock it down Permission models all around [Bridge] Shared clusters save your cost But isolation might get lost Dedicated gives you control Higher price but cleaner role Choose your path with workload size Traffic patterns, your compromise [Chorus] Multi-tenant, keep it separate Quotas guard what we don't waste Name your topics, set your ACLs Shared or dedicated, choose it well Multi-tenant, scaling right Kubernetes keeps it all in sight [Outro] Strimzi operators help you scale Multi-tenancy without fail From namespace walls to quota guards Your Kafka cluster playing cards
← 3 Cruise Control for Rebalancing | 4 GitOps & Infrastructure as Code →