StreamNative BYOC

Immutable Infrastructure:

Aligned with cloud-native computing philosophies.  the entire data plane can be described as code or configuration (e.g., Terraform states, Kubernetes manifests). This code and configuration can be used to rebuild the data plane, enabling quick migration from one location to another—from one public cloud to another, or between public and private clouds.

Atomicity

The data plane is atomic. You don’t need to worry about the bottleneck or single point of failure. Control plane can become lightweight and avoid being a bottleneck or a single point of failure, serving primarily as the orchestration layer.

Open

Our Portable Data Plane is built around Kubernetes, the cornerstone of cloud-native computing. We divided resource provisioning into two layers: Infrastructure and Workloads. The Infrastructure layer provisions workload pools, which are collections of Kubernetes clusters used for deploying workloads. A workload can be a Pulsar cluster, a UniConn connector, a Pulsar function, or a Flink job. The infrastructure layer is managed with Terraform. Within the workload pools, all workloads are defined as Custom Resources and managed by Kubernetes operators.

Secure

the access relies on open-standard. We can use cross-account IAM permissions for provisioning infrastructure or delegate infrastructure provisioning to the customer using our Terraform scripts.  We use Kubernetes API for manage workloads. No closed-source agents need to be installed—everything is executed via Kubernetes API and standards, ensuring an open approach. Changes are auditable through Kubernetes tools, allowing for self-auditing. Unlike other BYOC approaches, you do not have to blindly trust the vendor's promises.

Full Metadata & Data Control

Metadata service runs in your cloud, so your system remains operational even if the control plane fails.