Resources on StreamNative Cloud

StreamNative Cloud offers a variety of resources to help you build and manage data streaming applications. This section provides information about the top-level resources, organizations, instances, and workspaces, that you can use to organize your Pulsar/Kafka clusters, compute jobs (connectors, functions, and Flink jobs), and other StreamNative Cloud resources.

Organizations

The top-level resource in StreamNative Cloud is the organization. An organization is a logical grouping of resources that you can use to manage access to your StreamNative Cloud resources and to organize your resources in a way that makes sense for your organization. Most users will only need one organization, but you can create multiple organizations if you need to separate resources for different departments, teams, or customers.

To learn more about organizations, see Organizations.

Pools

Infrastructure Pools (abbreviated as Pools) are the underlying infrastructure resources that run workloads. Each pool encompasses a collection of infrastructure environments, known as Pool Members (abbreviated as PMs), distributed across multiple regions within a cloud provider. These Pool Members are equivalent to Kubernetes clusters dedicated to running workloads (such as Pulsar/Kafka clusters, Flink jobs, and other cloud resources). Organizations can have multiple pools to support different environments, such as development, testing, and production.

To learn more about pools, see Infrastructure Pools.

Workloads

StreamNative Cloud supports two major types of workloads: data workloads and compute workloads. Data workloads represents the running Kafka/Pulsar clusters that provides data storage and streaming capabilities. Compute workloads represents all the running computing jobs such as Flink jobs that can process data in real-time.

These workloads are logically grouped into instances and workspaces, respectively. They are allocated to different infrastructure pools to run.

Instances

Within each StreamNative Cloud organization, you can create one or more instances. Each instance can contain multiple clusters and deployed components, such as connectors and functions. Different departments or teams can use separate instances to isolate their resources and avoid interfering with each other. Organizations also often create multiple instances to support different environments, such as development, testing, and production.

To learn more about instances, see Instances.

Workspaces

While an instance is a logical grouping of data workloads (i.e., Pulsar/Kafka clusters), a workspace is a logical grouping of compute resources. Currently, workspaces are only supported for Flink jobs.