Resource model

SQIP uses a hierarchy to keep each organization's data and access separate.

Tenant

A tenant is the top-level customer boundary. Users, permissions, resources, usage, alerts, connectors, and audit events belong to a tenant.

Each tenant has:

A display name, such as Acme Streaming.
A slug, such as acme-streaming.
A status, normally active or suspended.

The display name can be friendly. The slug is a durable identifier and should be short, lowercase, and stable.

The Pulsar Clusters page attaches a tenant to the managed shared data plane. The first tenant may trigger initial platform preparation; later tenants reuse the same managed capacity while remaining logically isolated.

Create namespaces only after the cluster association reaches ready.

Namespace

A namespace groups topics that share an access and capacity boundary. Typical namespaces represent an environment or business domain:

orders-prod
payments-test
analytics-dev

Every namespace has a hard storage quota in whole GiB. SQIP warns when usage approaches the quota and blocks producers when the configured hard limit is reached.

Topic

A topic is a named stream of records. Producers write records and consumers read them independently.

Topic names support letters, numbers, dots, dashes, and underscores. Use a predictable naming convention such as:

domain.event
orders.created
orders.updated
payments.authorized

Partition

A partition allows a topic to process records in parallel. One partition is the simplest choice and preserves one ordered stream. More partitions can increase throughput, but ordering is guaranteed only within each partition.

Tip

Start with one partition unless your application needs more throughput and knows how to choose message keys consistently.

Schema

A schema defines the expected structure of records on a topic. SQIP supports Avro, Protobuf, and JSON schema files. A schema can evolve through new versions as long as it follows the namespace's compatibility policy.

Resource ownership

Resources never float between tenants. The selected tenant determines which clusters, namespaces, topics, API keys, connectors, and logs are available in each form.

Warning