Namespaces and topics

Namespaces and topics form the foundation of every SQIP data flow. A namespace controls the scope for storage and application access; a topic represents one stream of records.

Design namespaces around ownership

A good namespace contains topics with the same environment, operational owner, and access requirements.

Recommended examples:

orders-prod
orders-test
payments-prod
analytics-dev

Avoid placing unrelated production and test streams in the same namespace. API keys are namespace-scoped, so unrelated topics in one namespace are harder to isolate.

Set the storage quota

The Hard storage quota (GiB) is the maximum logical storage allowed for the namespace. Enter a positive whole number.

SQIP tracks two related values:

Logical storage is the retained message data for the namespace.
Capacity is the underlying storage available to the shared platform.

SQIP opens a warning when namespace usage reaches 80% of its quota and marks it critical at 100%. Producers may be held when the hard quota is reached.

Tip

Set notifications before a production launch so the team can respond before a namespace reaches its hard limit.

Inspect and change a namespace

Open Namespace and use the actions beside a managed namespace:

Details shows the tenant, cluster, storage, topics, and live connectivity information.
Quota changes the hard storage quota. Enter a positive whole number of GiB.
Reconcile asks SQIP to reapply the saved namespace configuration and refresh its observed state.
Delete permanently removes the namespace after its dependent resources are removed.

Name topics consistently

Topic names support letters, numbers, dots, dashes, and underscores. Prefer names that describe the business event rather than the producing application.

Prefer	Avoid	Why
`orders.created`	`service-a-output`	The event meaning remains clear when applications change
`payments.authorized`	`payment-data`	The event action is explicit
`inventory.updated`	`inventory-v2-final`	Version history belongs in schemas and applications

Choose a partition count

Choice	Best for	Trade-off
`1` partition	New or low-volume streams; simplest ordering	Limited parallel throughput
Multiple partitions	Higher throughput and parallel consumers	Ordering is limited to each partition

If you use multiple partitions, producers should set stable message keys so related records consistently reach the same partition.

Safe deletion order

Before deleting a namespace:

Pause or remove connectors that use its topics.
Stop applications that produce or consume.
Confirm that required data has been retained elsewhere.
Delete the topics in the namespace.
Delete the namespace.

Warning

Deleting a managed topic removes its broker data. SQIP does not provide an undo action.