TechPrufer
Get started
Temporal
Temporal logoTemporal · Feature trail

Temporal Nexus

6 posts · Oct 2024 – Dec 2025

What this trail covers

Temporal Nexus provides a durable abstraction for inter-service communication, enabling long-lived, guaranteed operations between services across isolated namespaces. It acts as a network of durable bridges, ensuring that operations initiated across services are completed with at-least-once and exactly-once semantics, regardless of duration or intermediate failures. Nexus uses Temporal's queue-based Worker architecture and built-in machinery for reliable execution, automatic retries, circuit breakers, and multi-region connectivity across AWS and GCP in Temporal Cloud. It supports Nexus Operation handlers in Temporal Workers, Nexus Endpoints as reverse proxies, and enhanced capabilities in Temporal Cloud including policy enforcement, auditing, and multi-region targets. The roadmap focuses on expanding connectivity, multi-language SDK support, and enhanced operational control.

All Temporal trails
  1. The city of systems: Temporal, Kafka, and NexusThis post introduces Temporal Nexus as a new infrastructure component that acts as 'durable bridges' connecting services. It explains how Nexus ensures operations initiated between services are completed with certainty, regardless of duration or failures, providing exactly-once semantics. This is positioned as a complement to Kafka's event broadcasting and Temporal's workflow orchestration, enabling direct, guaranteed inter-service operations that can span seconds, minutes, or days.
  2. Temporal Nexus is now generally availableThis post announces the General Availability of Temporal Nexus. It details how Nexus enables inter-service communication across isolated namespaces and regions with durable execution guarantees. Key features include Nexus Operation handlers, Nexus Endpoints, at-least-once and exactly-once execution, and integrated observability. Temporal Cloud enhancements include multi-region connectivity, access control, and auditing. The post also outlines the roadmap for future development, focusing on broader connectivity, multi-language support, and enhanced operational features.
  3. Replay 2025: New Temporal Capabilities for Faster DevelopmentTemporal 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.
  4. Announcing Nexus: Connect Temporal Applications across isolated NamespacesThis post announces Temporal Nexus, a new feature for connecting Temporal Applications across isolated namespaces. It introduces Nexus Endpoints, Nexus Services, and Nexus Operations, detailing how to build and use them with Temporal SDKs (Go and Java initially). Key technical contributions include: a reverse proxy (Nexus Endpoint) for decoupling callers from handlers, routing to specific namespaces and task queues, support for synchronous and asynchronous operations, integration with Temporal's queue-based Worker architecture for reliable execution, and built-in machinery for at-least-once/exactly-once guarantees, retries, circuit breaking, rate limiting, and load balancing. The post also outlines the roadmap for Nexus, including multi-cloud connectivity, GA release, and broader SDK support.
  5. Efficient GPU resource management with TemporalThis post details the adoption of Temporal Nexus within a GPU resource management platform. The platform uses child workflows for task management and is evolving to leverage Nexus for seamless integration of different workflows. The engineer highlights Nexus as a 'game-changer' for extensibility and mentions migrating parts of the platform to use it, indicating a move towards more integrated and flexible workflow orchestration across services.
  7. Making Temporal Cloud a Multi-Cloud PlatformThis post details Temporal Cloud's expansion to Google Cloud, complementing its existing AWS infrastructure. It highlights the challenges of multi-cloud deployments, including provider-specific Kubernetes annotations and Infrastructure-as-Code (IaC) differences (e.g., AWS vs. GCP load balancer configurations). The post emphasizes how Temporal's own capabilities, particularly its durable execution and cloud-agnostic workflows, were instrumental in managing this expansion. It also touches upon the need for abstraction layers to handle cross-provider discrepancies, such as the different approaches required for visibility layers (AWS OpenSearch vs. a third-party solution for GCP).