Skip to main content

What is a Temporal Namespace?

This guide provides a comprehensive overview of Namespaces.

A Namespace is a unit of isolation within the Temporal Platform.

A single Namespace is still multi-tenant.

Usage​

Namespaces are created on the Temporal Service, and provide a range of controls to achieve isolation on Workflow Executions.

  • Namespaces are a mechanism for resource isolation. Heavy traffic from one Namespace will not impact other Namespaces running on the same Temporal Service. For example, you can use Namespaces to match the development lifecycle by having separate dev and prod Namespaces.
  • If no other Namespace is specified, the Temporal Service uses the Namespace "default" for all Temporal SDKs and the Temporal CLI. See the Registration section for details.
  • Namespaces created on self-hosted Temporal Service are case-sensitive. For example, foo and Foo are two different Namespaces. On Temporal Cloud, Namespaces are case-insensitive, and we recommend using lowercase for Namespace names to avoid potential issues.
  • Membership: Task Queue names and Workflow Ids must all correspond to a specific Namespace. For example, when a Workflow Execution is spawned, it does so within a specific Namespace.
  • Uniqueness: Temporal guarantees a unique Workflow Id within a Namespace. Workflow Executions may have the same Workflow Id if they are in different Namespaces.
  • Namespace Configuration: Various configuration options like the Retention Period and the Archival destination are configured per Namespace through a special CRUD API or through the Temporal CLI.

Registration​

Registering a Namespace creates the Namespace on the Temporal Service. When you register your Namespace, you must also set the Retention Period for the Namespace.

On Temporal Cloud, use the Temporal Cloud UI or tcld commands to create and manage Namespaces.

On self-hosted Temporal Service, you can register your Namespaces using the Temporal CLI (recommended) or programmatically using APIs. Note that these APIs and Temporal CLI commands will not work with Temporal Cloud.

All SDKs require a Namespace on the Temporal Service (or Temporal Cloud) for their Client calls. If not set using Client options, the Workflow Client API looks for the default Namespace. If there is no default Namespace registered with your Temporal Service (or Temporal Cloud), all calls will throw errors. You must register your Namespace with the Temporal Service (or Temporal Cloud) before setting it in your Client.

On self-hosted Temporal Service, you can register your Namespaces in the following ways:

  • In your Temporal Service setup, create your Namespaces, including the default, in your setup script. For example:

    • If deploying through Docker Compose or using the auto-setup image in a custom Docker Compose application, the Namespace "default" is created, through the auto-setup script.
    • If deploying through the Temporal Helm charts, you can create the "default" Namespace by using the Temporal CLI; for example, temporal operator namespace create --namespace default

  • Use the temporal operator namespace create or temporal operator namespace update command with the --retention modfiier to register your Namespaces, one at a time, and set the Retention Period on each.

  • In your Client program, register your Namespace using RegisterNamespaceRequest API available in all the SDKs.

Note that registering a Namespace takes up to 15 seconds to complete. Ensure that you are waiting for this process to complete before making calls to the Namespace.

Manage Namespaces​

Use a custom Authorizer on your Frontend Service in the Temporal Service to set restrictions on who can create, update, or deprecate Namespaces.

On Temporal Cloud, use the Temporal Cloud UI or tcld commands to manage Namespaces.

On self-hosted Temporal Service, you can manage your registered Namespaces using the Temporal CLI (recommended) or programmatically using APIs.

  • How to manage Namespaces using the Go SDK

  • How to manage Namespaces using the Java SDK

  • Update information and configuration for a registered Namespace on your Temporal Service:

  • Get details for a registered Namespace on your Temporal Service:

  • Get details for all registered Namespaces on your Temporal Service:

    • With the Temporal CLI: temporal operator namespace list
    • Use the List Namespace API to return information and configuration details for all registered Namespaces on your Temporal Service.

  • Deprecate a Namespace: The Deprecate Namespace updates the state of a registered Namespace to "DEPRECATED". Once a Namespace is deprecated, you cannot start new Workflow Executions on it. All existing and running Workflow Executions on a deprecated Namespace will continue to run.

  • Delete a Namespace: Deletes a Namespace and all Workflow Executions on the Namespace. Note that this API is supported for Temporal Server version 1.17 and later.

  • With the Temporal CLI: temporal operator namespace delete.

  • Use the DeleteNamespace API to delete a registered Namespaces. All the running Workflow Executions on a deleted Namespace are also deleted.

Setting​

Set Namespaces in your SDK Client to isolate your Workflow Executions to the Namespace. If you do not set a Namespace, all Workflow Executions started using the Client will be associated with the "default" Namespace. This means, you must have a default Namespace called "default" registered with your Temporal Service. See Registration for details.

What is a Global Namespace?​

A Global Namespace is a Namespace that exists across Clusters when Multi-Cluster Replication is set up.

The Global Namespace feature enables Workflow Executions to progress through another Cluster in the event of a failover.

A Global Namespace may be replicated to any number of Clusters, but is active in only one Cluster at any given time.

For a failover to be successful, Worker Processes must be polling for Tasks for the Global Namespace on all Clusters.

A Global Namespace has a failover version. Because a failover can be triggered from any Cluster, the failover version prevents certain conflicts from occurring if a failover is mistakenly triggered simultaneously on two Clusters.

Only the active Cluster dispatches Tasks; however, certain conflicts are possible. Unlike regular Namespaces, which provide at-most-once semantics for an Activity Execution, Global Namespaces can support only at-least-once semantics (see Conflict resolution). Worker Processes on the standby Clusters are idle until a failover occurs and their Cluster becomes active.

Temporal Application API calls made to a non-active Cluster are rejected with a NamespaceNotActiveError which contains the name of the current active Cluster. It is the responsibility of the Temporal Application to call the Cluster that is currently active.