BlogsVercelDatabase Failover and Resilience Testing

Database Failover and Resilience Testing

Database Failover and Resilience Testing

1
posts
2025

Vercel successfully performed a full production failover of its core control-plane database from Azure West US to East US 2 with zero customer impact. This exercise involved testing all control-plane traffic, including API requests, background jobs, and deployment/build operations. While preview and development traffic routing was affected, production CDN traffic, served by a separate globally-replicated DynamoDB architecture, remained isolated. The preparation involved addressing issues with proprietary Cosmos DB clients lacking failover awareness, patching delays in write region detection from five minutes to five milliseconds, and resolving partition-level inconsistencies during failover. The live exercise confirmed system resilience, with all services remaining operational and on-call teams managing events effectively. Lessons learned from this graceful failover and previous staging tests are informing the near-term roadmap for more aggressive offline region operations and edge cases in write traffic transition.

2025

Preparing for the worst: Our core database failover test

8/28/2025

This post details the successful execution of a full production failover of Vercel's core control-plane database from Azure West US to East US 2. It highlights the motivation for rigorous disaster recovery testing, the architectural design for resilience across 19 regions, and the specific engineering challenges encountered and resolved during preparation. These challenges included making proprietary Cosmos DB clients failover-aware by programmatically updating write targets at runtime, reducing write region detection delays from five minutes to five milliseconds, and addressing partition-level inconsistencies during failover. The post also describes the live exercise, its operational impact, and the validation of the on-call team's readiness through alert and runbook integration. Lessons learned from both graceful and staged offline failovers are being used to inform the product roadmap.