Nexus Endpoints
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 proxy
A Nexus Endpoint acts as a reverse proxy for a single Nexus Service, routing requests to one target Namespace and Task Queue.
Unlike general-purpose proxies, it does not route to multiple backends. Instead, it provides a secure, managed connection to a specific upstream target, which can be in any region or cloud. The EndpointSpec support the following target type:
- Worker: Route to a target Namespace and Task Queue.
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.