Anastasia Vela's guest appearances

Anastasia Vela

Streaming Audio: Apache Kafka® & Real-Time Data

Jason Bell

Sam Ritchie

Kent Beck

Cornelia Davis

Anna McDonald

Kelsey Hightower

Lena Hall

Jay Smith

Matt Simpson

Colin McCabe

Sam Newman

Josh Long

Gwen Shapira

Paul Rayner

Dylan Scott

OwlTail

Anna Povzner

In an effort to make Apache Kafka® cloud native, Anna Povzener (Principal Engineer, Confluent) and Anastasia Vela (Software Engineer I, Confluent) have been working to expand multi-tenancy to cloud-native systems with automated capacity planning and scaling in Confluent Cloud. They explain how cloud-native data systems are different from legacy databases and share the technical requirements needed to create multi-tenancy for managed Kafka as a service. As a distributed system, Kafka is designed to support multi-tenant systems by: Isolating data with authentication, authorization, and encryptionIsolating user namespacesIsolating performance with quotasTraditionally, Kafka’s multi-tenant capabilities are used in on-premises data centers to make data available and accessible across the company—a single company would run a multi-tenant Kafka cluster with all its workloads to stream data across organizations. Some processes behind setting up multi-tenant Kafka clusters are manual with the requirement to over-provision resources and capacity in order to protect the cluster from unplanned demand increases. When Kafka is on cloud instances, you have the ability to scale cloud resources on the fly for any unplanned workloads to meet expectations instantaneously. To shift multi-tenancy to the cloud, Anna and Anastasia identify the following as essential for the architectural design: Abstractions: requires minimal operational complexity of a cloud servicePay-per-use model: requires the system to use only the minimum required resources until additional is necessary Uptime and performance SLA/SLO: requires support for unknown and unpredictable workloads with minimal operational workload while protecting the cluster from distributed denial-of-service (DDoS) attacksCost-efficiency: requires a lower cost of ownership You can also read more about the shift from on-premises to cloud-native, multi-tenant services in Anna and Anastasia’s publication on the Confluent blog. EPISODE LINKSFrom On-Prem to Cloud-Native: Multi-Tenancy in Confluent CloudCloud-Native Apache KafkaJoin the Confluent CommunityLearn more with Kafka tutorials, resources, and guides at Confluent DeveloperLive demo: Intro to Event-Driven Microservices with ConfluentUse PODCAST100 to get an additional $100 of free Confluent Cloud usage (details)Watch the video version of this podcast

In an effort to make Apache Kafka® cloud native, Anna Povzener (Principal Engineer, Confluent) and Anastasia Vela (Software Engineer I, Confluent) have been working to expand multi-tenancy to cloud-native systems with automated capacity planning and scaling in Confluent Cloud. They explain how cloud-native data systems are different from legacy databases and share the technical requirements needed to create multi-tenancy for managed Kafka as a service. As a distributed system, Kafka is designed to support multi-tenant systems by: <ul><li>Isolating data with authentication, authorization, and encryption</li><li>Isolating user namespaces</li><li>Isolating performance with quotas</li></ul>Traditionally, Kafka’s multi-tenant capabilities are used in on-premises data centers to make data available and accessible across the company—a single company would run a multi-tenant Kafka cluster with all its workloads to stream data across organizations. Some processes behind setting up multi-tenant Kafka clusters are manual with the requirement to over-provision resources and capacity in order to protect the cluster from unplanned demand increases. When Kafka is on cloud instances, you have the ability to scale cloud resources on the fly for any unplanned workloads to meet expectations instantaneously. To shift multi-tenancy to the cloud, Anna and Anastasia identify the following as essential for the architectural design: <ul><li>Abstractions: requires minimal operational complexity of a cloud service</li><li>Pay-per-use model: requires the system to use only the minimum required resources until additional is necessary </li><li>Uptime and performance SLA/SLO: requires support for unknown and unpredictable workloads with minimal operational workload while protecting the cluster from distributed denial-of-service (DDoS) attacks</li><li>Cost-efficiency: requires a lower cost of ownership </li></ul>You can also read more about the shift from on-premises to cloud-native, multi-tenant services in Anna and Anastasia’s publication on the Confluent blog.  EPISODE LINKS<ul><li><a href="https://www.confluent.io/blog/cloud-native-multi-tenant-kafka-with-confluent-cloud/" rel="nofollow" target="_blank">From On-Prem to Cloud-Native: Multi-Tenancy in Confluent Cloud</a></li><li><a href="https://developer.confluent.io/learn/cloud-native-kafka/" rel="nofollow" target="_blank">Cloud-Native Apache Kafka</a></li><li><a href="https://www.confluent.io/community/ask-the-community/" rel="nofollow" target="_blank">Join the Confluent Community</a></li><li><a href="https://developer.confluent.io/" rel="nofollow" target="_blank">Learn more with Kafka tutorials, resources, and guides at Confluent Developer</a></li><li><a href="https://www.confluent.io/resources/online-talk/demo-intro-to-event-driven-microservices-with-confluent/" rel="nofollow" target="_blank">Live demo: Intro to Event-Driven Microservices with Confluent</a></li><li><a href="https://www.confluent.io/confluent-cloud/tryfree" rel="nofollow" target="_blank">Use PODCAST100 to get an additional $100 of free Confluent Cloud usage</a> (<a href="https://www.confluent.io/confluent-cloud-promo-disclaimer/" rel="nofollow" target="_blank">details</a>)</li><li><a href="https://www.youtube.com/watch?v=8ti63z3idbs&amp;list=PLa7VYi0yPIH1B0i7mhzVi78TIkKSd-0vE" rel="nofollow" target="_blank">Watch the video version of this podcast</a></li></ul>

Expanding Apache Kafka Multi-Tenancy for Cloud-Native Systems ft. Anna Povzner and Anastasia Vela