
< session />
Thu, April 23BackEndArchitectureOpsTech
As event-driven systems grow, Kafka often becomes a core platform component. However, true multi-tenancy, governance, and cross-team collaboration require engineering beyond Kafka’s default capabilities. This session explores how Tesco built a secure, API-first Kafka streaming platform that supports dozens of teams, enforces strict tenant isolation, enables controlled cross-domain access, and provides active/active replication across regions.
The talk combines architecture, platform engineering, and practical lessons from operating a multi-tenant system that processes billions of events each day. You will see how automation, clear ownership models, quotas, and governance APIs transform Kafka from a cluster-centric setup into a scalable, enterprise-ready streaming platform.
What You Will Learn
Why Kafka’s native model falls short for enterprise multi-tenancy and how to address it
How an API-first management layer enforces governance, RBAC, quotas, and configuration safety
Isolation strategies, replication patterns, and operational lessons from running a large multi-tenant Kafka platform in production
Who Should Attend
Backend engineers
Platform engineers
Software architects
Site reliability engineers
Technology leaders building or scaling event-driven and multi-tenant platforms
< speaker_info />
Kshitiz Anand is an SDE-III at Tesco Bengaluru with over 12+ years of experience designing and scaling backend and platform ecosystems for large enterprises. His work spans product engineering, platform architecture, and reliability-led system design, shaping business-critical workloads at significant scale. He specializes in platform engineering and architecture, with a strong focus on building enterprise-grade, multi-tenant platforms that balance scale, tenant isolation, security, and operational excellence. Kshitiz has designed shared platforms that act as foundational building blocks for multiple teams and domains, establishing architectural guardrails, consistency, and self-service capabilities while preserving team autonomy. His approach prioritizes resilience, evolvability, and long-term sustainability over short-term optimization.