AnnouncementsUsing Temporal

3/6/2025

Temporal Nexus is Now Generally Available
headshot-megan-speare

Meagan Speare

Manager, Product Marketing

Today, we’re excited to announce that Temporal Nexus is now generally available! Nexus allows you to connect Temporal Applications within and across isolated Namespaces and provides all the benefits of Durable Execution with improved modularity, security, debugging, and fault isolation.

Unlike other forms of inter-service communication, Nexus is built with Durable Execution in mind. It combines a familiar programming model with the resiliency of Temporal to provide reliable state-based execution, built-in observability, and multi-region connectivity in Temporal Cloud across AWS and GCP.

temporal-nexus-blog-image

Used in production by companies like Netflix and Miro

Temporal Nexus is used by companies like Netflix and Miro to connect Temporal Applications across teams, Namespaces, and cloud regions.

Netflix aims to allow each team to own their own Namespace and call into each other to build abstractions on top of each other’s Workflows. When a Durable Execution spans teams, you often want to delegate a portion of the overall Workflow to another team with Workflows running in a different Namespace, but want a clean service contract that doesn’t share too much. Miro needed to enable cross-region data migration with a hierarchy of complex Workflows that took days or weeks to complete across isolated regions with no network connectivity or entry points for remote execution.

Previously, this required building custom API proxies and webhooks to facilitate cross-namespace collaboration. Teams had to handle complex tasks like setting up authentication and authorization (AuthZ), ensuring security, and managing cross-namespace failure scenarios. This was a lot of undifferentiated heavy lifting that could be simplified and even then you didn’t get first-class observability and execution debugging.

A fully integrated Temporal experience

Nexus GA provides a fully integrated Temporal experience where you can use the Temporal SDK to spin up Nexus Operation handlers in Temporal Workers that expose clean service contracts for others to use through a Nexus Endpoint, which is a reverse proxy for your Nexus Services. Nexus Operations are used to abstract underlying Temporal primitives, like Workflows, or execute arbitrary code. Nexus calls can be made from caller Workflows within and across Namespace boundaries, which solves the immediate problem of cross-namespace calls in Temporal.

Nexus GA is supported in both the Open Source and Temporal Cloud, and enables you to:

  • Build Nexus Services with the Go SDK & Java SDK - others coming soon!
  • Run Nexus Services with Temporal’s queue-based Worker architecture.
  • Use Nexus Operations through a Nexus Endpoint, a reverse proxy for Nexus Services.
  • Enhance reliability with at-least-once and exactly-once execution guarantees.
  • Secure sensitive Workflow state with isolated Namespaces for each team.
  • Debug cross-namespace calls with integrated observability.

Temporal Cloud provides enhanced Nexus capabilities:

  • Connect Temporal Applications within and across regions in AWS and GCP.
  • Control access to Nexus Endpoints with built-in policy enforcement.
  • Audit changes to Nexus Endpoints and monitor Nexus metrics.

Since the Nexus Public Preview was announced last year, Nexus GA has been focused on:

  • Enhanced stress testing and hardening.
  • SDK ergonomics: tracing, error rehydration, and metrics failure tagging.
  • Circuit breaker visibility and enhanced bi-directional links in the Temporal UI.
  • Multi-cloud Nexus connectivity across AWS and GCP in Temporal Cloud.
  • Support for multi-region Namespaces as Nexus Endpoint targets in Temporal Cloud.
  • Terraform support for managing Nexus Endpoints in Temporal Cloud.

The road ahead

The Nexus roadmap is currently focused on 3 key themes:

Connect from more places:

  • Nexus calls from non-workflow callers (bash, service, app)
  • Non-namespace credentials to establish a Nexus caller identity
  • Connect OSS and Temporal Cloud

Develop in any language with a better developer experience:

  • All Temporal SDKs support Nexus
  • SDK ergonomics and richer semantics
  • Service contract IDL & code generation

Operate shared services with enhanced visibility & control:

  • Multi-tenant visibility and rate limiting
  • Fine-grained authorization
  • Enhanced routing rules

Get started with Nexus today!

Learn how Nexus connects Temporal Applications and provides all the benefits of Durable Execution within and across Namespace boundaries with improved modularity, security, debugging, and fault isolation.