Cluster Types & Regions in StreamNative Cloud

StreamNative offers various cluster types in the StreamNative Cloud. The type of cluster you choose impacts its features, capabilities, and cost. Utilize this guide to identify the cluster that best meets your requirements. Use Serverless clusters for experimentation and early development. For a production cluster, choose from Dedicated (formerly Hosted) clusters, BYOC, or BYOC Pro clusters.

The table below offers a high-level comparison of features across StreamNative Cloud cluster types.

Serverless Clusters

Serverless clusters are the newest addition to StreamNative Cloud, offering a fully managed, auto-scaling solution with minimal operational overhead. Key features include:

1. Instant provisioning with zero base cost.
2. Automatic scaling based on your workload, with billing only for resources used.
3. Simplified management with StreamNative handling all infrastructure concerns.
4. Ideal for development, testing, and production workloads with variable traffic patterns.

StreamNative uses Elastic Throughput Units (ETUs) to provision and bill for the Serverless clusters.

ETU limits per Serverless cluster

Serverless clusters are elastic, shrinking and expanding automatically based on load. You don't need to size your cluster. When you need more capacity, your Serverless cluster expands up to the fixed maximum. If you're not using any capacity, you're not paying for it.

Serverless cluster capacity

If consumption in a given hour is zero across all billable dimensions, you pay nothing. For more information, see Elastic Throughput Unit (ETU).

ETU capacity guidance

The dimensions in the following table describe the capacity of a single ETU. For more information about ETU, see Elastic Throughput Unit (ETU) and ETU vs CU/SU.

Serverless limits per cluster

Serverless limits per partition

The partition capabilities that follow are based on benchmarking and intended as practical guidelines for planning purposes. Performance per partition will vary based on your specific configuration, and these benchmarks do not guarantee performance.

Serverless Cloud Providers & Regions

Serverless clusters are currently available in limited regions. Please check the StreamNative Cloud console for the most up-to-date information on available regions.

Serverless Features and Usage Limits

Currently, Serverless clusters are in Public Preview. The usage limits are not strictly enforced, but you should expect some limitations. Here are some guidelines for the cluster limits:

In addition to the usage limits, there are some additional limitations in features:

1. Tiered Storage is transparent, meaning you don't need to configure it. However, Serverless clusters don't support bringing your own bucket. If you need to use your own object storage bucket, you should consider using BYOC or BYOC Pro clusters.

2. Serverless clusters use Rapid Release Channel by default. You can't choose a different release channel.

3. Auto-scaling is enabled by default. You don't need to configure it.

4. Remote writes to external observability systems are not supported.

5. Custom maintenance windows are not available.

6. Private networking options are not available.

Dedicated Clusters

Dedicated (formerly Hosted) clusters are fully managed on StreamNative's cloud infrastructure. They support the following capabilities:

1. Deployment in supported regions on AWS, GCP, and Azure with a 99.95% uptime SLA for Single-Zone and 99.99% for Multi-Zone.

2. Optional multi-zone high availability, spreading a cluster across three availability zones for enhanced resilience.

3. Simplified scaling in terms of Compute Units (CUs) and Storage Units (SUs).

4. Programmable or automatic scaling options.

Dedicated Cloud Providers & Regions

The following is a list of cloud providers along with the regions and zones supported for Dedicated (formerly Hosted) Clusters:

AWS

GCP

Azure

Dedicated Features and Usage Limits

The following table outlines the features and usage limits for the Dedicated (formerly Hosted) Clusters:

In addition to the above, there are additional limitations in Dedicated (formerly Hosted) clusters:

1. Tiered Storage is transparent, meaning you don't need to configure it. However, Dedicated clusters don't support bringing your own bucket. If you need to use your own bucket, you should consider using BYOC or BYOC Pro clusters.

2. Remote writes to external observability systems are not supported.

3. Custom maintenance windows are not available.

4. Private networking options are not available.

BYOC Clusters

BYOC clusters are designed for production-ready deployments in your Cloud account, tailored to meet your data security, compliance, and sovereignty requirements. They offer the following capabilities:

1. Dedicated deployments in your chosen region within your cloud account (AWS, GCP, Azure) with a 99.95% uptime SLA for Single-Zone and 99.99% for Multi-Zone.

2. Private networking options including AWS PrivateLink, Azure PrivateLink, and GCP Private Service Connect.

3. Optional multi-zone high availability, spreading a cluster across three availability zones for increased resilience.

4. Simplified scaling in terms of CUs and SUs.

5. Programmable or automatic scaling options.

6. You can choose between Classic Engine and Ursa Engine.

StreamNative uses CU/SU to bill for the Classic Engine clusters and uses Elastic Throughput Units (ETUs) to for the Ursa Engine clusters.

BYOC Cloud Providers & Regions

A BYOC cluster can be deployed in any selected region in your cloud account across AWS, GCP, and Azure.

BYOC Features and Usage Limits

1. The performance limit is majorly bound by the underlying resources of your cloud account.

2. You can access most of the Pulsar and URSA features in your BYOC clusters.

3. You can use your own S3-compatible storage bucket for the Ursa Engine or Lakehouse tiered storage for the Classic Engine.

4. You can use your own keys for data-at-rest encryption.

5. Only PrivateLink is supported for private networking. Other private networking options are not supported. You can manually configure them if you choose to use a different private networking option, but it will be out of scope for StreamNative support.

6. Geo-replication via private networking is not supported. Only public networking geo-replication is supported. If you need geo-replication via private networking, you should consider using BYOC Pro.

7. Remote writes to external observability systems are not supported.

8. Custom maintenance windows are not available.

ETU capacity guidance

The dimensions in the following table describe the capacity of a single ETU in a Ursa Engine BYOC cluster. For more information about ETUs, see Elastic Throughput Unit (ETU) and ETU vs CU/SU.

BYOC Pro Clusters

BYOC Pro Clusters are designed for critical production workloads and offer enhanced security and networking features, including:

1. Advanced private networking options like VPC/VNet Peering and Transit Gateway.

2. Remote writes to external observability systems.

3. Lakehouse tiered storage solutions.

4. Self-managed keys (Bring-Your-Own-Key) for AWS, Azure, or GCP.

Similar to BYOC clusters, BYOC Pro uses CU/SU to bill for Classic Engine clusters and uses Elastic Throughput Units (ETUs) for Ursa Engine clusters.

BYOC Pro Cloud Providers & Regions

BYOC Pro Clusters can be deployed in any selected region in your cloud account across AWS, GCP, and Azure.

BYOC Pro Features and Usage Limits

BYOC Pro is the most secure and flexible option, which provides you with full control over your data and network configurations.

1. The performance limit is majorly bound by the underlying resources of your cloud account.

2. You can access most of the Pulsar and URSA features in your BYOC Pro clusters.

3. You can use your own S3-compatible storage bucket for the Ursa Engine or Lakehouse tiered storage for the Classic Engine.

4. You can use your own keys for data-at-rest encryption.

5. Private Link, VPC/VNet Peering, and Transit Gateway are supported for private networking.

6. Geo-replication via private networking is supported.

ETU capacity guidance

The dimensions in the following table describe the capacity of a single ETU in a Ursa Engine BYOC Pro cluster. For more information about ETUs, see Elastic Throughput Unit (ETU) and ETU vs CU/SU.