Connect Temporal Applications Across Isolated Namespaces with Nexus

Abstract

Connecting workflows across teams, namespaces, regions, and clouds is critical for scaling modern distributed systems. Miro adopted Temporal to build a self-healing control plane for their storage infrastructure across multiple environments. They introduced it incrementally, starting with high-impact and time-consuming tasks such as pg_repack and later expanding to backfill new columns and enabling Teleport access across the fleet of sharded PostgreSQL clusters.

After this first Temporal use case was deployed to production, an increase in demand for cross-region data migration required orchestrating a hierarchy of complex workflows that took days or weeks to complete across isolated regions with no network connectivity or entry points for remote execution.

Temporal Nexus provides a built-in way to connect Temporal applications across isolated namespaces and regions in AWS. This enabled Miro to orchestrate moving data in any direction, across cloud regions, with a global workflow concept.

In this session, you’ll learn how to:

• Abstract Temporal primitives, like Workflows, with clean service contracts.
• Run Nexus Services in existing Workers with Temporal’s queue-based architecture.
• Use Nexus Operations through a Nexus Endpoint, a reverse proxy for Nexus Services.
• Connect within and across regions in AWS and GCP using Temporal Cloud.
• Improve reliability with at-least-once and exactly-once execution guarantees
• Simplify debugging and monitoring with built-in observability

This session offers practical insights into the future of a fully integrated Temporal experience and how Nexus reduces operational overhead, improves scalability, and connects Temporal applications across team, namespace, and region boundaries making collaboration easier and more efficient. Whether you're a developer, architect, or team lead, this talk will show you how to elevate your workflow orchestration.