new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Temporal · Concepts · all subjects

namespaces & isolation

11 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Deletion protection for Temporal Cloud production Namespaces

Enable deletion protection for production Namespaces in Temporal Cloud to prevent accidental deletion.

Namespace definition and purpose

A Namespace is a unit of isolation within the Temporal Platform. It ensures that Workflow Executions, Task Queues, and resources are logically separated, preventing conflicts and enabling safe multi-tenant usage.

Namespace naming convention: lowercase and hyphens

Use lowercase letters and hyphens as separators in Namespace names. Temporal Cloud Namespace names are case-insensitive so MyNamespace and mynamespace refer to the same Namespace. Open source Namespace names are case-sensitive so MyNamespace and mynamespace are different Namespaces. To avoid confusion across environments, always use lowercase.

Namespace naming pattern recommendation

Use a pattern like <use-case>-<domain>-<environment> to name Namespaces. Use case should be maximum 10 characters (examples: payments, fulfill, orders). Domain should be maximum 10 characters (examples: checkout, notify, inventory). Environment should be 3 characters (examples: dev, stg, prd). Examples of full names: payments-checkout-dev, fulfill-notify-prd, orders-inventory-stg. For Temporal Cloud, Namespace names are limited to 39 characters total.

Default Namespace behavior in SDK client

If you do not set a Namespace in your SDK Client, all Workflow Executions started using the Client will be associated with the default Namespace. You must register a Namespace before setting it in your Client.

Namespace boundary impacts in Temporal Cloud

In Temporal Cloud, a Namespace boundary affects APS limits and rate limiting, access control and credential scope, blast radius for misconfigured or overloaded Workers, observability boundaries for dashboards and alerts, and operational overhead for provisioning, tagging, and lifecycle management.

Workflow ID uniqueness with shared Namespaces

When multiple teams share a Namespace, prefix each Workflow ID with a service-specific string to ensure uniqueness. Task Queue names must also be unique within the Namespace.

Authorizer for open source Namespace management

Use a custom Authorizer on your Frontend Service to set restrictions on who can create, update, or deprecate Namespaces. If an Authorizer is not set, Temporal uses the nopAuthority authorizer that unconditionally allows all API calls. On Temporal Cloud, role-based access controls provide namespace-level authorization without custom configuration.

Infrastructure as Code for Temporal Cloud Namespaces

Use the Temporal Cloud Terraform provider to manage Namespaces. If Terraform is not suitable, scripting against the Cloud Ops API or tcld is a good alternative. This provides documentation of each Namespace's purpose and owners, prevention of infrastructure drift, and version-controlled configuration changes. Use prevent_destroy = true in your Terraform configuration to prevent accidental Namespace deletion via Terraform. This is separate from Temporal Cloud deletion protection which prevents deletion through any interface.

Namespace tags in Temporal Cloud

Tags are key-value metadata pairs that help organize, track, and manage Namespaces in Temporal Cloud. Tags complement your naming convention by adding metadata that doesn't fit in the Namespace name. While the name captures use case, domain, and environment, tags can capture additional dimensions like team ownership, data sensitivity, or business criticality.

Recommended Namespace tag categories

Recommended tag keys are: environment (examples: dev, staging, production) for deployment stage; team (examples: platform, payments, identity) for owning team; division (examples: engineering, finance, ops) for business unit; criticality (examples: high, medium, low) for business importance; data-sensitivity (examples: pii, pci, public) for data classification; latency-sensitivity (examples: realtime, batch, async) for performance tier.

Give your agent this brain

namespaces & isolation — Temporal · Concepts