Namespaces

Overview

A namespace is a container within a tenant used to organise and isolate system configuration in Cantara. Namespaces separate environments, such as development, testing, UAT, and production, ensuring configurations remain distinct and manageable.

Key Points

• Each namespace has a unique name and belongs to a specific tenant.

• Namespaces store configuration and log information; they do not store customer business data.

• Each namespace is assigned to a hosting region. The region can influence performance, data residency, and where related services are hosted.

• Agent and service keys are associated with a namespace and are used to support secure connectivity between Cantara components.

Planning Your Environment Structure

Namespaces allow you to isolate environments within a single tenant. Consider how many namespaces you'll need before starting. Common patterns include:

• Single namespace — Suitable for smaller deployments or initial setup where environment separation is not yet required.

• Environment-based (e.g., Development, Testing, Production) — The most common approach. Each environment gets its own namespace, allowing independent configuration and preventing changes in one environment from affecting another.

In most cases, create additional namespaces when environments require separate configuration or different hosting regions. Avoid creating unnecessary namespaces to keep administration straightforward.