TechPrufer
Get started
Temporal
Temporal logoTemporal · Feature trail

High Availability and Disaster Recovery for Temporal Cloud

5 posts · Mar 2024 – Nov 2025

What this trail covers

Temporal Cloud offers Multi-region Namespaces for high availability and disaster recovery, enabling active-standby setups with seamless failover during outages to meet a 99.99% SLA. This feature replicates workflows to a standby region, managed by Temporal Cloud without user configuration changes. Recent improvements focus on hardening the auto-failover mechanism to prevent dependencies on the source region and to trigger failovers earlier. Multi-region Replication is now Generally Available (GA).

All Temporal trails
  1. How developers kept running during the AWS us-east-1 outageThis post details a specific failure mode encountered during the AWS us-east-1 outage where an auto-failover workflow for Temporal Namespaces in us-east-1 was blocked due to a dependency on the source region, prolonging recovery time for a small number of customers. It also highlights the successful operation of proactively failed-over namespaces and the overall resilience of the multi-region replication feature. The post outlines plans to fix the auto-failover workflow dependency and improve network partition detection for faster failovers.
  2. Temporal Cloud Expands High Availability: Multi-Region & Same-Region ReplicationAnnounces the General Availability (GA) of Multi-region Replication (formerly Multi-region Namespaces) and the Public Preview of Same-region Replication for Temporal Cloud. Details the underlying replication mechanisms (database-level replication across AZs, cell-based architecture) and the concepts of Replica and Failover. Explains the benefits of HA features for business continuity and compliance (99.99% SLA). Mentions future pricing adjustments for multi-region replication related to network traffic and upcoming Multi-cloud Replication.
  3. Making Temporal Cloud a Multi-Cloud PlatformThis post details Temporal Cloud's expansion from AWS to Google Cloud, highlighting the technical challenges and solutions involved in becoming a multi-cloud platform. It discusses the limitations of standard containerization and orchestration tools (Kubernetes) and IaC tools (Terraform) when dealing with provider-specific APIs and resource models. Specific examples are provided for Kubernetes service annotations (AWS EKS vs. GCP GKE) and Terraform configurations for load balancers (AWS ALB vs. GCP HTTPS Load Balancer). The post also addresses the need for compatible visibility layers, noting the difference between AWS OpenSearch and Google Cloud's lack of a directly compatible ElasticSearch 7 equivalent. The core solution involved leveraging Temporal's durable execution capabilities to manage the complexity of multi-cloud deployments and ensure consistency.
  4. Maximize Uptime with Multi-Region Deployment and FailoverThis post announces the Public Preview of Multi-region Namespaces (formerly Global Namespaces), which provide a contractual SLA of 99.99% availability against service errors through an active-standby setup. Workflows are replicated by Temporal Cloud to a user-defined standby region, and in case of an outage in the active region, failover is seamless with no manual synchronization or code changes required. The technology has been dogfooded internally for over a year.
  5. High Availability & Disaster Recovery with Temporal CloudThis post details Temporal Cloud's high availability and disaster recovery capabilities. It outlines the challenges of self-hosting Temporal, including managing databases and multiple server services, and highlights Temporal Cloud's solutions: fault tolerance across three availability zones, a 99.99% SLO, and a 99.9% contractual SLA. For disaster recovery, it specifies zero RTO/RPO for AZ failures and a maximum of eight hours for region failures. It also announces the upcoming Multi-Region Namespaces feature, which will provide manual failover for regional outages and extend the SLA to 99.99%.