BlogsTemporalTemporal Nexus

Temporal Nexus

Temporal Nexus

5
posts
2024–2025

Temporal Nexus is now generally available, enabling the connection of Temporal Applications within and across isolated Namespaces. It provides Durable Execution benefits with improved modularity, security, debugging, and fault isolation. Nexus supports at-least-once and exactly-once execution guarantees, and in Temporal Cloud, offers multi-region connectivity across AWS and GCP, policy enforcement for Nexus Endpoints, and auditing capabilities. The roadmap includes expanding connectivity to non-Temporal services and enhancing its capabilities for cross-namespace and cross-cloud communication. This post further elaborates on Nexus as a 'durable promise' infrastructure, contrasting it with Kafka's broadcast model and Temporal's structured roads, highlighting its role in direct, guaranteed, long-duration operations between services.

2025

The city of systems: Temporal, Kafka, and Nexus

12/10/2025

This post introduces Temporal Nexus as a 'durable promise' infrastructure, contrasting it with Kafka's broadcast model and Temporal's structured roads. It explains Nexus's role in enabling direct, guaranteed, and long-duration operations between services, emphasizing its ability to hold promises until completion regardless of failures or duration. The post uses an analogy of 'durable bridges' connecting 'towns' (services) to illustrate Nexus's function in Systemville, where Kafka handles high-throughput freeways, Temporal manages structured local roads, and Nexus bridges connect services directly for operations of any duration, ensuring promises are kept exactly once.

Durable Digest: July 2025

7/29/2025

This post announces updates to Temporal Nexus, including the ability to have multiple callers starting operations backed by a single Workflow, associating Nexus links with their callbacks, and new operation cancellation types. It also mentions the general availability of Update-With-Start and the public preview of Worker Versioning and Task Queue Priority.

Temporal Nexus is now generally available

3/6/2025

This post announces the General Availability of Temporal Nexus, a new capability that allows Temporal Applications to connect within and across isolated Namespaces. It highlights Nexus's built-in Durable Execution, observability, and multi-region connectivity. Key features include building Nexus Services with Go and Java SDKs, running them with Temporal's queue-based Worker architecture, using Nexus Operations through Nexus Endpoints (reverse proxies), and achieving at-least-once and exactly-once execution guarantees. Temporal Cloud offers enhanced capabilities like multi-region connectivity, policy enforcement, and auditing. The post also details recent improvements from the public preview, such as stress testing, SDK ergonomics, circuit breaker visibility, multi-cloud connectivity, and Terraform support.

Replay 2025: New Temporal Capabilities for Faster Development

3/4/2025

Temporal Nexus is now Generally Available, enabling the connection of Temporal Applications across (and within) isolated Namespaces. This provides Durable Execution benefits across team and application boundaries with improved modularity, security, debugging, and fault isolation. Nexus GA enables users to abstract Temporal primitives, like Workflows, with clean service contracts; run Nexus Services in Workers with Temporal's queue-based architecture; use Nexus Operations through a Nexus Endpoint, a reverse proxy for Nexus Services; and connect within and across regions in AWS and GCP using Temporal Cloud. Temporal Cloud on Google Cloud now supports Nexus.

2024

Announcing Nexus: Connect Temporal Applications across isolated Namespaces

12/20/2024

This post announces the public preview of Temporal Nexus, a feature for connecting Temporal Applications across isolated Namespaces. It details how Nexus provides Durable Execution benefits with improved modularity, security, debugging, and fault isolation. The post explains the creation of Nexus Endpoints in the Nexus Registry, the architecture of Nexus Services and Operations, and how to build and use them with Temporal SDKs. It highlights at-least-once and exactly-once execution guarantees, and mentions future roadmap items like multi-cloud connectivity and support for external clients.