A StreamNative Instance represents a cohesive group of clusters functioning together as a unified entity.
Each instance is uniquely identified by a Uniform Resource Name (URN) that follows the structure urn:sn:pulsar:organization-id:pulsar-instance-name
. You can retrieve the organization name and instance name using the snctl get organizations <organization-id>
and snctl get pulsarinstance <instance-name>
commands, respectively. When a Pulsar client connects to a Pulsar cluster using OAuth2 authentication, this URN is required as audience to use for the authentication process.
After creating an organization, you can create one or more Serverless, Dedicated, or BYOC instances within that organization. However, before creating BYOC instances, you must first provision one or more BYOC infrastructure pools in your cloud accounts.
An Instance is a logical entity that groups one or more clusters. Clusters can be distributed across multiple geographic regions and replicated between them using geo-replication.
StreamNative supports three types of instances:
The availability mode of an instance determines how clusters are distributed across availability zones within a geographic region. StreamNative supports two availability modes:
Currently, StreamNative Cloud only supports the Regional availability mode. Support for Zonal availability mode will be available in a future release.
All the clusters within an instance must use the same availability mode.
An instance is deployed to one infrastructure pool, which can be either Fully Hosted (for Serverless and Dedicated instances) or BYOC (for BYOC instances). A pool reference identifies which pool will be used for deploying instances.
pool_namespace
is always set to streamnative
.pool_namespace
is set to the organization ID where the cloud environment was created.The data streaming engine of an instance determines which engine will be used for running the clusters within the instance. Below is a table that lists the supported engines for different instance types:
Instance Type | Classic Engine | Ursa Engine |
---|---|---|
Serverless | ✅ | ❌ |
Dedicated | ✅ | ❌ |
BYOC | ✅ | ✅ |
BYOC Pro | ✅ | ✅ |
After creating an instance, you can create a cluster within the instance.
A StreamNative Instance represents a cohesive group of clusters functioning together as a unified entity.
Each instance is uniquely identified by a Uniform Resource Name (URN) that follows the structure urn:sn:pulsar:organization-id:pulsar-instance-name
. You can retrieve the organization name and instance name using the snctl get organizations <organization-id>
and snctl get pulsarinstance <instance-name>
commands, respectively. When a Pulsar client connects to a Pulsar cluster using OAuth2 authentication, this URN is required as audience to use for the authentication process.
After creating an organization, you can create one or more Serverless, Dedicated, or BYOC instances within that organization. However, before creating BYOC instances, you must first provision one or more BYOC infrastructure pools in your cloud accounts.
An Instance is a logical entity that groups one or more clusters. Clusters can be distributed across multiple geographic regions and replicated between them using geo-replication.
StreamNative supports three types of instances:
The availability mode of an instance determines how clusters are distributed across availability zones within a geographic region. StreamNative supports two availability modes:
Currently, StreamNative Cloud only supports the Regional availability mode. Support for Zonal availability mode will be available in a future release.
All the clusters within an instance must use the same availability mode.
An instance is deployed to one infrastructure pool, which can be either Fully Hosted (for Serverless and Dedicated instances) or BYOC (for BYOC instances). A pool reference identifies which pool will be used for deploying instances.
pool_namespace
is always set to streamnative
.pool_namespace
is set to the organization ID where the cloud environment was created.The data streaming engine of an instance determines which engine will be used for running the clusters within the instance. Below is a table that lists the supported engines for different instance types:
Instance Type | Classic Engine | Ursa Engine |
---|---|---|
Serverless | ✅ | ❌ |
Dedicated | ✅ | ❌ |
BYOC | ✅ | ✅ |
BYOC Pro | ✅ | ✅ |
After creating an instance, you can create a cluster within the instance.