Nexus - Temporal Cloud feature guide
Temporal Nexus is now Generally Available. Learn why you should use Nexus in the evaluation guide.
Temporal Nexus allows you to connect Temporal Applications across (and within) isolated Namespaces. This provides all the benefits of Durable Execution across team and application boundaries with improved modularity, security, debugging, and fault isolation. Nexus supports cross-team, cross-domain, cross-namespace, multi-region, and multi-cloud use cases.
Nexus Overview
Temporal Cloud support is built on top of the core Nexus experience and adds a global Nexus Registry within an Account, enhanced security, and multi-region connectivity within and across AWS and GCP.
- Evaluate why you should use Nexus and learn more about Nexus use cases.
- Learn Nexus concepts in the Encyclopedia.
Global Nexus Registry
The Nexus Registry in Temporal Cloud is scoped to an Account. Workers in any Namespace can host Nexus Services for others to use within an Account.
Built-in access controls
Temporal Cloud has built-in Endpoint access controls to restrict which callers can use a Nexus Endpoint.
Audit logging
Temporal Cloud supports audit log streaming for Nexus Registry actions to create, update, or delete Endpoints.
Multi-region connectivity
Nexus requests in Temporal Cloud are routed across Namespaces, within and across AWS and GCP, using a global mTLS-secured Envoy mesh. Built-in Nexus Machinery provides reliable at-least-once execution and Workflow policy can deduplicate requests for exactly-once execution, even across multi-region boundaries.
Terraform support
The Terraform provider for Temporal Cloud supports managing Nexus Endpoints.
Learn more
- Evaluate why you should use Nexus and watch the Nexus keynote and demo.
- Learn key Nexus concepts and how Nexus works in the Nexus deep dive talk
- Explore additional resources to learn more about Nexus.