# Disaster Recovery Published articles for Disaster Recovery. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Presentation: How To Run on Three Clouds at Once, and When Not To DevFeed: [Presentation: How To Run on Three Clouds at Once, and When Not To]() Original publisher: [Read original article]() Author: Ross McFarlane, Kevin Holditch Published: 2026-09-11T11:00:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [networking](), [Databases](), [Kubernetes]() Tags: [amazon](), [architecture](), [architecture-design](), [availability](), [aws](), [cloud](), [cloud-architecture](), [cloud-computing](), [cloud-networking](), [cockroach-labs](), [cockroachdb](), [containers](), [databases](), [devops](), [disaster-recovery](), [engineering](), [europe](), [financial-applications](), [fintech](), [form3-multicloud-architecture](), [infoq](), [kubernetes](), [microservices](), [networking](), [presentation](), [qcon-london-2026](), [qcon-software-development-conference](), [resilience](), [transcripts](), [us]() ### AI overview A presentation on Form3's move from one cloud to a triple-active multi-cloud architecture, covering cross-cloud networking, distributed databases, Kubernetes operators, and regional disaster-recovery expectations. ### Source excerpt Ross McFarlane and Kevin Holditch discuss Form3's evolution from a single-cloud setup to a triple active multi-cloud architecture. They share key engineering strategies for cross-cloud networking, distributed databases with CockroachDB and NATS, custom Kubernetes operators, and navigating distinct regional disaster recovery expectations across the UK, Europe, and US financial markets. By Ross McFarlane, Kevin Holditch ## Kubernetes disaster recovery: Guidance from three reproducible failure scenarios DevFeed: [Kubernetes disaster recovery: Guidance from three reproducible failure scenarios]() Original publisher: [Read original article]() Author: Saiyam Pathak, Saloni Narang | CNCF Ambassadors Published: 2026-09-10T11:37:00Z Content type: article Language: en Sources: [Cloud Native Computing Foundation]() Topics: [Kubernetes](), [data](), [GitOps](), [postgresql clusters]() Tags: [blog](), [data](), [disaster-recovery](), [git](), [kubernetes](), [postgresql]() ### AI overview Guidance for recovering stateful Kubernetes applications through three reproducible failure scenarios, focusing on backup validation, declared versus stored state, and multi-volume consistency. ### Source excerpt Scope This document describes three failure scenarios that separate having backups from being able to recover, and the guidance that follows from each. Every scenario is reproducible on a laptop from the lab repository above, and... ## Validating multi-Region DR for Terraform Enterprise with AWS FIS DevFeed: [Validating multi-Region DR for Terraform Enterprise with AWS FIS]() Original publisher: [Read original article]() Author: Frenil Randeria Published: 2026-09-09T21:05:02Z Content type: article Language: en Sources: [AWS Architecture Blog]() Topics: [Terraform](), [AWS Fault Injection Service (FIS)](), [Chaos Engineering](), [Amazon S3](), [Amazon EC2](), [Databases]() Tags: [advanced-300](), [amazon-aurora](), [amazon-ec2](), [amazon-s3](), [aws](), [aws-fault-injection-service-fis](), [disaster-recovery](), [postgresql](), [technical-how-to](), [terraform](), [validation]() ### AI overview This article explains how to validate customer-operated multi-Region disaster recovery for Terraform Enterprise on AWS using three-phase AWS FIS experiments. It covers failover and failback testing, hidden dependency discovery, and reported recovery times of 12-14 minutes. ### Source excerpt Learn how AWS, HashiCorp, and Athenahealth designed and chaos-tested a multi-Region disaster recovery strategy for Terraform Enterprise on AWS. This post walks through three-phase AWS Fault Injection Service experiments across Amazon EC2, Aurora, and Amazon S3, the 12-14 minute recovery times achieved, and the state file dependency pitfall to avoid. ## PGConf India 2027 - Dates Announced and CFP Open DevFeed: [PGConf India 2027 - Dates Announced and CFP Open]() Original publisher: [Read original article]() Author: PGConf India Published: 2026-09-05T00:00:00Z Content type: news Language: en Sources: [PostgreSQL news]() Topics: [data](), [Replication]() Tags: [cloud](), [community](), [conference](), [data](), [data-platforms](), [disaster-recovery](), [monitoring](), [open-source](), [performance](), [postgres](), [security]() ### AI overview PGConf India 2027 will take place in Bengaluru from March 2-5, 2027. Its Call for Papers is open, with submissions due October 15, 2026, covering PostgreSQL topics including internals, performance, replication, cloud infrastructure, security, monitoring, production case studies, data platforms, extensions, and open source. ### Source excerpt Hey there, Mark your calendars: PGConf India 2027 is set for March 2-5, 2027 at the Sheraton Grand Hotel at Brigade Gateway, Bengaluru. The Call for Papers is open right now. Important dates CFP closes -- October 15, 2026 We tell you yes/no -- November 15, 2026 The actual conference -- March 2-5, 2027 What we're into Basically anything Postgres, including but not limited to: Core internals & features Performance & query tuning HA, replication & disaster recovery Cloud & infra Security & compliance Monitoring & ops Real production case studies ML, analytics & data platforms (pgvector fans, this means you) Extensions & ecosystem tools Community & open source To submit Give us a title, session length (25 or 40 min), your bio, and an abstract (≤500 words) on what you'll say and what people should walk away with. Submit your talk Ticket sales aren't open yet -- watch pgconf.in for that and everything else. See you in Bengaluru. The PGConf India Team https://pgconf.in Powered By ConfBase.io ## Kubernetes Backup and Disaster Recovery: What to Protect and How? DevFeed: [Kubernetes Backup and Disaster Recovery: What to Protect and How?]() Original publisher: [Read original article]() Author: Urolime Technologies Published: 2026-09-04T14:50:25Z Content type: article Language: en Sources: [Kubernetes Archives - Urolime Blogs]() Topics: [Kubernetes](), [Disaster Recovery](), [Availability](), [Cloud Native Ecosystem]() Tags: [applications](), [availability](), [backup](), [cloud-native](), [disaster-recovery](), [kubernetes](), [kubernetes-backup-and-disaster-recovery]() ### AI overview The article explains that Kubernetes high availability and self-healing do not provide disaster recovery. It describes why Kubernetes backup is complex and identifies persistent data, Kubernetes resources, configurations, secrets, and cluster configuration as protection targets, along with several disaster scenarios. ### Source excerpt Kubernetes has been the bedrock on which most modern-day cloud-native apps have been built- thus providing organizations with a highly efficient way of deploying and managing their workloads. The self-healing nature, automatic scaling, and high availability features of Kubernetes give a false sense that applications are inherently resilient against failures. However, high availability is not [...] ## Forging India's Digital Future: Elastic{ON} Comes to Mumbai DevFeed: [Forging India's Digital Future: Elastic{ON} Comes to Mumbai]() Original publisher: [Read original article]() Author: Atul Ahuja Published: 2026-08-26T00:00:00Z Content type: article Language: en Sources: [Elastic Blog - Elasticsearch, Kibana, and ELK Stack]() Topics: [AI search](), [telemetry]() Tags: [agentic-ai](), [agentic-ai-cybersecurity](), [ai-agents](), [cybersecurity](), [data](), [disaster-recovery](), [india](), [observability](), [observability-security-search](), [resilience](), [search](), [security]() ### AI overview Elastic{ON} Mumbai will cover search, full-stack observability, security, and the use of enterprise data to ground agentic AI. The article also discusses regulatory expectations for unified, real-time technology visibility, resilience, and evidence production. ### Source excerpt Join us at Elastic{ON} Mumbai to explore search, full-stack observability, and security, and how Elastic acts as the context engine that grounds agentic AI in your enterprise data, transforming regulatory mandates and data into an AI advantage. ## Push-button migration from Confluent to Redpanda with Shadowing DevFeed: [Push-button migration from Confluent to Redpanda with Shadowing]() Original publisher: [Read original article]() Author: Trevor Blackford Published: 2026-08-25T00:00:00Z Content type: article Language: en Sources: [Redpanda]() Topics: [migration](), [Replication](), [Kafka](), [Confluent Cloud](), [Confluent Platform](), [Disaster Recovery](), [Usability]() Tags: [big-bang](), [confluent-cloud](), [confluent-platform](), [data-centers](), [disaster-recovery](), [kafka](), [migration](), [replication](), [schema]() ### AI overview The article presents Redpanda Shadowing 26.2 as a low-risk migration path from Confluent Cloud, Confluent Platform, or other Apache Kafka-compatible clusters. It replicates topic data, schemas, offsets, and ACLs while preserving offsets, allowing teams to validate workloads and move applications individually instead of using a big-bang cutover. ### Source excerpt Migrate off Confluent without the "big cutover weekend." Redpanda Shadowing carries topic data, schemas, offsets, and ACLs on a single link. Available on Self-Managed , BYOC, and Dedicated. ## Recovery strategies to meet data residency requirements DevFeed: [Recovery strategies to meet data residency requirements]() Original publisher: [Read original article]() Author: Jamie Pasterick Published: 2026-08-13T14:05:39Z Content type: article Language: en Sources: [AWS Architecture Blog]() Topics: [data](), [Cryptography]() Tags: [advanced-300](), [aws](), [best-practices](), [cloud](), [data](), [disaster-recovery](), [encryption](), [infrastructure](), [replication]() ### AI overview The article presents three disaster-recovery strategies for critical AWS workloads that must meet data-residency requirements, ranging from encryption-based controls for multi-Region replication to fully in-country architectures. ### Source excerpt Learn three strategies for achieving disaster recovery while meeting data residency requirements. Ranging from encryption-based controls on multi-Region replication to fully in-country architectures, these patterns help you balance recovery objectives with regulatory constraints. ## Multi-Region PostgreSQL Disaster Recovery and Failback with Crunchy PGO DevFeed: [Multi-Region PostgreSQL Disaster Recovery and Failback with Crunchy PGO]() Original publisher: [Read original article]() Author: Wellingtone Luvonga Published: 2026-08-11T05:00:00Z Content type: tutorial Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [PostgreSQL](), [Disaster Recovery](), [Kubernetes](), [MinIO](), [nginx](), [TLS (Transport Layer Security)](), [Amazon S3](), [Availability]() Tags: [availability](), [backup](), [data-recovery](), [disaster-recovery](), [failover](), [high-availability](), [how-to](), [kubernetes](), [minio](), [nginx](), [postgresql](), [recovery](), [s3](), [tls](), [tutorials]() ### AI overview A tutorial on using Crunchy PostgreSQL Operator on Kubernetes to implement multi-region PostgreSQL disaster recovery and failback. It covers secure MinIO-backed WAL storage through an NGINX TLS reverse proxy, regional failover, and reversing roles without timeline conflicts or archive poisoning. ### Source excerpt This blog talks about multiregion PostgreSQL disaster recovery using Crunchy PGO. It has some detailed steps to understand better. The post Multi-Region PostgreSQL Disaster Recovery and Failback with Crunchy PGO appeared first on CYBERTEC PostgreSQL | Services & Support. ## Disaster Recovery Testing Best Practices for 2026 DevFeed: [Disaster Recovery Testing Best Practices for 2026]() Original publisher: [Read original article]() Author: Pritesh Kiri Published: 2026-08-04T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [Disaster Recovery](), [Testing](), [Resilience](), [Automation]() Tags: [2026](), [audit](), [automated](), [automation](), [best-practices](), [cross-functional-teams](), [disaster-recovery](), [external](), [metrics](), [pipelines](), [recovery](), [resilience](), [testing]() ### AI overview This article explains how to evolve disaster recovery testing from reactive exercises into a mature, metrics-driven resilience program. It covers risk-aligned testing schedules, automation, continuous improvement, and metrics for demonstrating recovery effectiveness. ### Source excerpt Learn how to move from ad hoc DR tests to a mature, metrics-driven resilience program with risk-aligned schedules, automation, and the KPIs that prove your reco | Blog ## Introducing self-managed Amazon S3 buckets for AWS Lambda function code DevFeed: [Introducing self-managed Amazon S3 buckets for AWS Lambda function code]() Original publisher: [Read original article]() Author: Doug Perkes Published: 2026-07-17T10:49:14Z Content type: release Language: en Sources: [AWS Compute Blog]() Topics: [AWS Lambda](), [Amazon S3](), [Deployment](), [Security](), [Replication](), [CI/CD](), [AWS Organizations]() Tags: [amazon-s3](), [amazon-simple-storage-service-s3](), [audit-trail](), [aws](), [aws-lambda](), [aws-organizations](), [ci-cd](), [compliance](), [deployment](), [disaster-recovery](), [encryption](), [replication](), [security](), [uncategorized]() ### AI overview AWS Lambda now supports self-managed Amazon S3 buckets for function deployment packages. Lambda reads code directly from the customer-controlled bucket, removing deployment-package copies from the Lambda code storage quota and giving teams control over encryption, access policies, compliance, lifecycle management, audit trails, and cross-Region replication. ### Source excerpt If you manage Lambda functions at scale, you've likely hit the 75 GB code storage limit or explained to your security team why deployment artifacts live in an S3 bucket you don't control. Today, we're announcing self-managed Amazon S3 buckets for AWS Lambda deployment packages. Lambda reads your code directly from your bucket, eliminating quota [...] ## Announcing Upvest as Confluent's 2026 EMEA Data Streaming Startup of the Year DevFeed: [Announcing Upvest as Confluent's 2026 EMEA Data Streaming Startup of the Year]() Original publisher: [Read original article]() Author: Tim Graczewski Published: 2026-07-16T00:07:01Z Content type: article Language: en Sources: [Confluent: Data in motion]() Topics: [Streaming](), [real-time](), [Resilience](), [event driven](), [Scalability](), [Cloud](), [data-governance](), [Microservices](), [Architecture & Design](), [Disaster Recovery]() Tags: [2026](), [cloud](), [cloud-native](), [compliance](), [confluent](), [confluent-cloud](), [data](), [data-governance](), [disaster-recovery](), [emea](), [event-driven](), [fintech](), [infrastructure](), [microservices](), [real-time](), [resilience](), [revolut](), [scalability](), [startup](), [streaming]() ### AI overview Confluent recognizes Berlin-based Upvest as its inaugural EMEA Data Streaming Startup of the Year. The article describes Upvest's real-time, event-driven fintech infrastructure, which supports embedded investments, client onboarding, data governance, disaster recovery, scalability, and regulatory resilience for major financial institutions. ### Source excerpt Confluent for Startups provides an easy on-ramp to Confluent Cloud for early stage startups with great data streaming use cases. ## Top System Design Performance Metrics DevFeed: [Top System Design Performance Metrics]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-07-14T08:36:41Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [benchmarking](), [Availability](), [Architecture & Design](), [Scalability](), [Load Balancing](), [health checks](), [Concurrency](), [Disaster Recovery](), [Database](), [sharding](), [IO](), [API]() Tags: [api](), [availability](), [blocking](), [concurrency](), [database](), [disaster-recovery](), [health-checks](), [load-balancing](), [performance](), [performance-metrics](), [scalability](), [sharding](), [system-design]() ### AI overview A tutorial on system design performance metrics, focusing on availability and throughput. It explains how these metrics are measured and outlines techniques such as load balancing, health checks, failover, redundancy, disaster recovery, query optimization, sharding, and asynchronous processing. ### Source excerpt Must Know Metrics ## How to Automate CockroachDB Operations with AI Using Cockroach University DevFeed: [How to Automate CockroachDB Operations with AI Using Cockroach University]() Original publisher: [Read original article]() Author: Nathan Zamecnik Published: 2026-07-13T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Agent Skills](), [Artificial Intelligence](), [maintenance](), [Claude Code](), [Disaster Recovery](), [Security](), [observability]() Tags: [agent-skills](), [agents](), [ai-agents](), [claude-code](), [cockroachdb](), [disaster-recovery](), [maintenance](), [observability](), [security]() ### AI overview The article describes CockroachDB Agent Skills, a public repository of machine-executable operational workflows that AI agents such as Claude Code and Cursor can use. It also introduces three Cockroach University courses covering rolling restarts, encryption at rest, and planned node maintenance, along with a free trial of the CockroachDB Training Subscription. ### Source excerpt AI agents aren't just changing how applications interact with databases, they're changing how teams operate them. ## DASH 2026 Operating at Scale: Guide to Datadog's newest announcements DevFeed: [DASH 2026 Operating at Scale: Guide to Datadog's newest announcements]() Original publisher: [Read original article]() Author: Datadog Published: 2026-06-09T00:00:00Z Content type: news Language: en Sources: [Datadog | The Monitor blog]() Topics: [SDKs](), [incident]() Tags: [ai](), [announcements](), [cloud](), [cost](), [dash](), [disaster-recovery](), [incident](), [observability](), [outage](), [remote](), [scale](), [sdks]() ### AI overview A DASH 2026 announcement roundup covering tools for operating Datadog deployments at scale, including Disaster Recovery, remote SDK upgrades, and organization-level administration. ### Source excerpt A roundup of everything we announced at DASH 2026, including proactive AI spend attribution, Disaster Recovery, and remote SDK upgrades. ## Me and my shadow (link!): Disaster recovery replication made easy DevFeed: [Me and my shadow (link!): Disaster recovery replication made easy]() Original publisher: [Read original article]() Author: Paul Wilkinson Published: 2026-04-21T00:00:00Z Content type: article Language: en Sources: [Redpanda]() Topics: [Disaster Recovery](), [Replication](), [Streaming](), [systems](), [API](), [Kafka]() Tags: [disaster-recovery](), [enterprise](), [failover](), [kafka](), [operational](), [outage](), [real-time](), [replication](), [streaming]() ### AI overview This article explains Redpanda Shadow Linking as a built-in disaster recovery feature for continuous replication between streaming clusters. It describes an active-passive architecture in which a read-only shadow cluster receives topics, schemas, offsets, ACLs, commits, and messages, then becomes writable after failover. ### Source excerpt Shadow Linking made simple. Get started with real-time replication. ## Introducing the SQL Server on Kubernetes Operator DevFeed: [Introducing the SQL Server on Kubernetes Operator]() Original publisher: [Read original article]() Author: Anthony Nocentino Published: 2026-04-12T05:00:00Z Content type: tutorial Language: en Sources: [Kubernetes on Anthony Nocentino's Blog]() Topics: [Kubernetes](), [sql-server](), [Availability](), [Disaster Recovery](), [Open Source]() Tags: [automated](), [automatic](), [availability](), [availability-groups](), [containers](), [disaster-recovery](), [failover](), [high-availability](), [kubernetes](), [open-source](), [operator](), [sql-server]() ### AI overview This tutorial introduces sql-on-k8s-operator, an open-source Kubernetes operator for managing SQL Server workloads. It addresses high availability and disaster recovery by automating lifecycle management, failover, and Always On Availability Group setup, and demonstrates deployment with custom resources. ### Source excerpt Are you considering replatforming your SQL Server workload due to recent vendor changes, but still need high availability and disaster recovery? You're not alone. One of the challenges with running SQL Server on Kubernetes is that there's no Kubernetes operator available. That means no automated lifecycle management, no automatic failover, and no standard way to bootstrap an Always On Availability Group on Kubernetes. I'm excited to share it today as an open-source project: sql-on-k8s-operator. Let's go. ## v18.2.8 Reef released DevFeed: [v18.2.8 Reef released]() Original publisher: [Read original article]() Author: Yuri Weinstein Published: 2026-03-20T00:00:00Z Content type: release Language: en Sources: [Ceph Blog]() Topics: [Vulnerabilities](), [Security](), [configuration](), [SSL](), [Disaster Recovery](), [data]() Tags: [2026](), [aws](), [blog-post](), [bug](), [configuration](), [disaster-recovery](), [en-article](), [en-blog-post](), [reef](), [release](), [security](), [ssl](), [vulnerability]() ### AI overview Ceph v18.2.8 Reef is the eighth and expected final backport release in the Reef series, released on March 20, 2026. It includes upgrade guidance, security fixes for CephFS clients and Mgr Alerts, RGW and CephFS reliability fixes, configurable JWKS URL verification for AWS compliance, and additional MDS and CephFS changes. ### Source excerpt This is the eighth, and expected to be last, backport release in the Reef series. We recommend that all users update to this release. Release Date ¶ March 20, 2026 Known Issues ¶ During QA for v18.2.8, it was found that there was a bug for upgrades from Pacific to Reef. Pacific OSDs (and other Ceph daemons) were still using a deprecated connection feature bit that was adopted to indicate a Reef OSD. This can cause a OSD_UPGRADE_FINISHED warning before all OSDs are actually upgraded to Reef. There are no known issues associated with Pacific and Reef OSDs interoperating where Pacific OSDs are "advertising" Reef compatibility; however, out of an abundance of caution, we no longer recommend upgrading from Pacific to Reef directly. Security Fixes ¶ CephFS Client: A fix was merged to prohibit unprivileged users from modifying the sgid or suid bits on a file. Previously, unprivileged users were inadvertently permitted to set these bits if they were the sole bits being modified. Mgr Alerts: The SMTP SSL context was enforced in the mgr/alerts module to resolve a security vulnerability (GHSA-xj9f-7g59-m4jx). Notable Changes ¶ RGW (RADOS Gateway): Fixed an issue where bucket rm --bypass-gc was mistakenly removing head objects instead of tail objects, potentially causing data inconsistencies. Fixed rgw-restore-bucket-index to handle objects with leading hyphens and to process versioned buckets correctly. Addressed an issue in the msg/async protocol that caused memory locks and hangs during connection shutdown. RGW STS: Made JWKS URL verification configurable for AWS compliance via the rgw_enable_jwks_url_verification configuration. CephFS / MDS: Prevented the MDS from stalling (up to 5 seconds) during rename/stat workloads by forcing the log to nudge for unstable locks after early replies. Fixed cephfs-journal-tool so it no longer incorrectly resets the journal trim position during disaster recovery, which was causing stale journal objects to linger forever in the metadata pool ## How Gremlin makes disaster recovery testing easier and faster DevFeed: [How Gremlin makes disaster recovery testing easier and faster]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2026-03-04T00:00:00Z Content type: tutorial Language: en Sources: [Gremlin Blog]() Topics: [Disaster Recovery](), [Resilience](), [Testing](), [Cloud]() Tags: [backup](), [cloud](), [disaster-recovery](), [failover](), [gremlin](), [resilience](), [testing](), [use-cases]() ### AI overview The article explains how Gremlin's Disaster Recovery Testing helps teams test disaster recovery plans by simulating failures such as zone evacuations, region failovers, and cloud-provider outages. It recommends establishing service baselines with test suites, running tests regularly, and repeating them to verify fixes. ### Source excerpt Gremlin's Disaster Recovery Testing makes it easy to run zone evacuations, region failovers, and more for a fraction of the lift of traditional disaster recovery testing. ## Aloha, Redpanda FY27 company kick-off DevFeed: [Aloha, Redpanda FY27 company kick-off]() Original publisher: [Read original article]() Author: Jenny Medeiros Published: 2026-02-24T00:00:00Z Content type: article Language: en Sources: [Redpanda]() Topics: [AI Infrastructure](), [Redpanda-Connect](), [Serverless](), [Amazon Web Services](), [Disaster Recovery](), [MCP Server](), [Graphs](), [Google]() Tags: [ai](), [ai-infrastructure](), [aws](), [disaster-recovery](), [google](), [graphs](), [mcp-server](), [redpanda-connect](), [serverless]() ### AI overview Redpanda's FY27 company kick-off brought more than 160 employees together in San Diego to reflect on the company's progress and direction. The article highlights the Agentic Data Plane, Redpanda Cloud, Redpanda Serverless on AWS, disaster recovery in Redpanda 25.3, MCP server development, and new Redpanda Connect connectors, alongside talks about company culture and using AI to reshape work. ### Source excerpt From AI hackathons to hakas, here's what happened at our fourth company kick-off. ## Temporal raises $300M Series D at a $5B valuation as AI drives demand for Durable Execution DevFeed: [Temporal raises $300M Series D at a $5B valuation as AI drives demand for Durable Execution]() Original publisher: [Read original article]() Author: Allanah Hughes Published: 2026-02-17T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [distributed-systems](), [Artificial Intelligence](), [Orchestration](), [Cloud](), [Disaster Recovery](), [backends]() Tags: [agentic-ai](), [ai](), [ai-agents](), [announcements](), [backends](), [cloud](), [disaster-recovery](), [distributed-systems](), [fault-tolerance](), [orchestration]() ### AI overview Temporal announces a $300 million Series D at a $5 billion post-money valuation, led by Andreessen Horowitz. The company says demand for durable execution is increasing as AI and other long-running production workflows require state preservation and recoverable failures. ### Source excerpt Temporal raises $300M Series D at a $5B valuation as AI drives demand for Durable Execution. ## Announcing Disaster Recovery Testing DevFeed: [Announcing Disaster Recovery Testing]() Original publisher: [Read original article]() Author: Andre Newman Published: 2026-02-03T00:00:00Z Content type: release Language: en Sources: [Gremlin Blog]() Topics: [Disaster Recovery](), [Testing](), [Incident response](), [Resilience](), [Availability](), [Cloud](), [datacenter](), [Amazon Web Services](), [Azure]() Tags: [announcements](), [availability](), [aws](), [azure](), [disaster-recovery](), [failover](), [gremlin](), [health-checks](), [incident-response](), [infrastructure](), [metrics](), [resilience](), [systems](), [testing]() ### AI overview Gremlin announces Disaster Recovery Testing, a feature for running organization-wide zone, region, and datacenter-scale experiments. It helps teams validate failover, disaster recovery, and incident response processes, with health checks that can automatically halt tests when key metrics exceed defined SLA limits. ### Source excerpt Gremlin announces Disaster Recovery Testing for validating region failover processes, disaster recovery plans, incident response procedures, and more. ## Durable under pressure: How developers kept running during the AWS us-east-1 outage DevFeed: [Durable under pressure: How developers kept running during the AWS us-east-1 outage]() Original publisher: [Read original article]() Author: Luke Knepper Published: 2025-11-07T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Amazon Web Services](), [Availability](), [Cloud](), [Disaster Recovery](), [Replication](), [incident](), [DynamoDB]() Tags: [2025](), [availability](), [aws](), [disaster-recovery](), [dynamodb](), [high-availability](), [incident](), [outage](), [temporal-concepts](), [us]() ### AI overview The article examines the October 20, 2025 AWS us-east-1 outage and explains how multi-region high availability and disaster recovery strategies helped some applications continue running. It describes Temporal Cloud's replication and failover features and FireHydrant's preparation and testing. ### Source excerpt The AWS us-east-1 outage affected many, but some devs were able to stay afloat. Find out how. ## Redpanda 25.3 delivers near-instant disaster recovery and more DevFeed: [Redpanda 25.3 delivers near-instant disaster recovery and more]() Original publisher: [Read original article]() Author: Matt Schumpert Published: 2025-11-06T00:00:00Z Content type: release Language: en Sources: [Redpanda]() Topics: [Disaster Recovery](), [Resilience](), [Kafka](), [Streaming](), [Availability](), [configuration](), [Cloud](), [API](), [systems]() Tags: [cloud](), [clusters](), [configuration](), [consumer](), [disaster-recovery](), [high-availability](), [integration](), [kafka](), [process](), [production](), [real-time](), [recovery](), [release](), [resilience](), [server](), [stream-processing](), [streaming](), [systems](), [update]() ### AI overview The article previews Redpanda 25.3, focusing on Shadowing, a disaster recovery and business continuity feature for streaming workloads. Shadowing creates a byte-for-byte, offset-preserving hot standby of a production cluster in another region, including topics, configurations, consumer offsets, ACLs, and schemas. It is designed to provide recovery point and recovery time objectives measured in seconds, with setup through configuration or Redpanda Console and replication using the standard Kafka API. ### Source excerpt Check out how the latest Redpanda release is providing the resilience, efficiency, and interoperability that modern enterprises need for their streaming workloads. [Next page]()