Skip to main content

Nexus Endpoints

SUPPORT, STABILITY, and DEPENDENCY INFO

Temporal Nexus is now Generally Available for Temporal Cloud and self-hosted deployments.

A Temporal Nexus Endpoint is a reverse proxy that can route Nexus requests from a caller Workflow to an upstream target Namespace and Task Queue. A Nexus Service runs in a Worker that is polling the Endpoint's target Task Queue.

An Endpoint decouples the caller and handler, so the caller only needs to know the Endpoint name. The Endpoint encapsulates the upstream target Namespace and Task Queue from the caller. A Worker handles Nexus requests by registering one or more Nexus Services and polling the Endpoint's target Task Queue.

Nexus Overview

Nexus Overview

Multiple Nexus Endpoints can target different Task Queues in the same target Namespace.

Reverse proxy for Nexus Services, not a general purpose L7 proxy​

A Temporal Nexus Endpoint is a reverse proxy for Nexus Services. It is not a general purpose L7 reverse proxy like NGINX which can route arbitrary HTTP requests to different upstream targets. A Nexus Endpoint currently supports routing Nexus requests to a single upstream target. The Temporal Nexus EndpointSpec has two Endpoint target types:

  • Worker: route Nexus requests to a target Namespace and Task Queue.
  • External (experimental): route Nexus requests to an external target Nexus RPC endpoint with experimental support in temporal operator nexus create endpoint for --target-url which may be used with the Nexus Registry in a self-hosted Temporal Service.

Deploying a Nexus Endpoint​

Adding a Nexus Endpoint to the Nexus Registry deploys the Endpoint in the Temporal Service, so it is available at runtime to serve Nexus requests.