Skip to main content
Cluster Profile A cluster profile is a preconfigured performance and cost setting that determines how a data streaming cluster behaves based on its underlying storage, latency expectations, and workload characteristics. Each profile packages the right combination of infrastructure choices—such as disk-based storage for low-latency access or object storage for cost-efficient retention—to deliver a predictable experience without requiring users to tune individual parameters. By selecting a cluster profile, users can align their cluster with the needs of their applications, whether they prioritize real-time responsiveness, throughput, or cost optimization. Cluster Profile Types Latency-Optimized Cluster Profile: The Latency-Optimized cluster profile is designed for real-time, interactive, and mission-critical workloads that require consistently fast data access and low end-to-end latency. Backed by high-performance disk storage, this profile delivers predictable, single-digit to tens-of-milliseconds latency for producers and consumers, making it ideal for use cases such as event processing, fraud detection, user activity tracking, and any application where responsiveness directly impacts user experience or business outcomes. By prioritizing speed over cost, the Latency-Optimized profile ensures smooth, high-throughput performance even under demanding conditions. image of Latency Optimized Cluster Profile A StreamNative cluster using the latency-optimized profile is expected to deliver end-to-end latencies in the 5–200 millisecond range. The infrastructure underpinning the Latency Optimized profile is based on StreamNative Cloud’s original Apache Pulsar architecture leveraging ZooKeeper and BookKeeper, and it also provides full Kafka compatibility. Cost-Optimized Cluster Profile: The Cost-Optimized cluster profile is engineered for throughput-intensive and cost-sensitive workloads that benefit from large-scale, durable, and economical object storage. While this profile accepts higher access latencies—typically in the hundreds of milliseconds—it provides significant cost savings and unlimited scalability, making it a strong fit for data pipelines, analytics sinks, long-term retention, and applications that do not require ultra-fast consumption. By leveraging object storage, the Cost-Optimized profile offers an efficient balance of price, durability, and flexibility for workloads where latency tolerance is higher and storage economics matter most. image of Latency Optimized Cluster Profile A StreamNative cluster using the cost-optimized profile is expected to deliver end-to-end latencies above 200 milliseconds. The infrastructure associated with the Cost Optimized profile is built on Ursa engine, our next-generation, cloud-native architecture designed for long-term scalability and cost efficiency. It evolves core design and implementation principles to deliver a more flexible and highly scalable architecture. The Cost Optimized profile leverages Oxia for metadata management and uses object storage systems—such as Amazon S3, Google Cloud Storage, and Azure Blob Storage—as its underlying data persistence layer. Cluster Profiles Support - Deployment Options
Deployment OptionLatency OptimizedCost Optimized
ServerlessNANA
DedicatedSupportedNot supported (Coming soon)
Bring Your Own Cloud (BYOC)SupportedSupported
Cluster Profiles - Supported features based on deployment type Deployment Type - Serverless
CategoryFeatures
ProtocolKafka, Pulsar
Table FormatsDelta, Iceberg
CatalogUnity, Snowflake Open Catalog, S3 Tables
StorageDisk (internal only)
Availability ZoneSingle AZ (internal only)
Note : Cluster profiles do not apply to Serverless deployments, as Serverless automatically manages performance and cost characteristics without user-defined profiles. Deployment Type - Dedicated
CategoryFeatures On Latency Optimized ProfileFeatures On Cost Optimized Profile
ProtocolKafka, PulsarNot available
Table FormatsDelta, IcebergNot available
CatalogUnity Catalog, Snowflake Open Catalog, S3 TablesNot available
StorageDiskNot available
Availability ZoneSingle AZ (Not available), Multi AZNot available
Deployment Type - BYOC
CategoryFeatures On Latency Optimized ProfileFeatures On Cost Optimized Profile
ProtocolKafka, PulsarKafka, Pulsar (Not Available)
Table FormatsDelta, IcebergDelta, Iceberg
CatalogUnity Catalog, Snowflake Open Catalog, S3 TablesUnity, Snowflake Open Catalog, S3 Tables
StorageDiskObject Storage
Availability ZoneSingle AZ (Not available), Multi AZSingle AZ (Not available), Multi AZ