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 Nexus Endpoint is a fully managed reverse proxy for Nexus Services. It routes requests from a caller Workflow to a target Namespace and Task Queue. Callers only need to know the Endpoint name - the target Namespace, Task Queue, and internal implementation are encapsulated.

Workers handle Nexus requests by registering one or more Services and polling the Endpoint's target Task Queue. Multiple Endpoints can target different Task Queues in the same Namespace.

The Endpoint description field supports markdown for documenting available Operations, contact information, or schema links.

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

A Nexus Endpoint is not a general-purpose L7 proxy. It routes Nexus requests to a single upstream target. The EndpointSpec supports two target types:

  • Worker: Route to a target Namespace and Task Queue.
  • External (experimental): Route to an external Nexus RPC endpoint using --target-url in temporal operator nexus create endpoint (self-hosted only).

Deploying a Nexus Endpoint​

Adding an Endpoint to the Nexus Registry deploys it immediately. The Endpoint is available at runtime as soon as it's registered.