Multi-Cloud Active-Active Temporal Cluster (AWS + OCI) with Dual Entry Points

Community Support
,
1

Hi Team,

I’m designing a multi-cloud deployment for Temporal across AWS and OCI, and I’d like guidance on the recommended architecture and limitations.

Architecture Goal

I want to run Temporal in:

  • Cloud A → AWS
  • Cloud B → OCI

Both clusters should be independently reachable and capable of handling client traffic at all times.

Traffic Model

  • Some users will initially be routed to AWS
  • Some users will be routed to OCI
  • Later, I may want to migrate entirely to OCI
  • During migration, both clusters must accept workflow starts

Both clusters must be able to handle:

StartWorkflowExecution
SignalWorkflowExecution
QueryWorkflow
Worker task polling

At any point in time, users may be routed to either AWS or OCI. I do not want a strict active-passive setup where only one cluster accepts traffic (Eventual Consistency Is Acceptable)

Is this achievable using Temporal’s Global Namespace + Multi-Cluster Replication?
Does Temporal support true active-active where:

  • Workflows can be started in both clusters
  • Both clusters are configured as active for the same namespace?
2

Does Temporal support true active-active where:
Workflows can be started in both clusters
Both clusters are configured as active for the same namespace?

No this is not supported currently. In order to achieve something like this for same namespace you would have to form a single cluster across aws and oci which can introduce additional latencies.

What the actual use case where you need such setup and have to use same namespace?