Uber's Failover Architecture: Reconciling Reliability and Efficiency in Hyperscale Microservice Infrastructure
Fuente:
arXiv
Saved in:
| Main Authors: | , , , , , , , , , , , , , , , , , , , , , , |
|---|---|
| Format: | Preprint |
| Published: |
2026
|
| Subjects: | |
| Online Access: | |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| _version_ | 1866915842781872128 |
|---|---|
| author | Bansal, Mayank Chabbi, Milind Bogh, Kenneth Prodduturi, Srikanth Xu, Kevin Kumar, Amit Bell, David Dey, Ranjib Ren, Yufei Sharma, Sachin Marcano, Juan Kale, Shriniket Pradhan, Subhav Beschastnikh, Ivan Covarrubias, Miguel Liao, Chien-Chih Sheshadri, Sandeep Koushik Luo, Wen Song, Kai Samant, Ashish Rihan, Sahil Sheth, Nimish Medisetty, Uday Kiran |
| author_facet | Bansal, Mayank Chabbi, Milind Bogh, Kenneth Prodduturi, Srikanth Xu, Kevin Kumar, Amit Bell, David Dey, Ranjib Ren, Yufei Sharma, Sachin Marcano, Juan Kale, Shriniket Pradhan, Subhav Beschastnikh, Ivan Covarrubias, Miguel Liao, Chien-Chih Sheshadri, Sandeep Koushik Luo, Wen Song, Kai Samant, Ashish Rihan, Sahil Sheth, Nimish Medisetty, Uday Kiran |
| contents | Operating a global, real-time platform at Uber's scale requires infrastructure that is both resilient and cost-efficient. Historically, reliability was ensured through a costly 2x capacity model--each service provisioned to handle global traffic independently across two regions--leaving half the fleet idle. We present Uber's Failover Architecture (UFA), which replaces the uniform 2x model with a differentiated architecture aligned to business criticality. Critical services retain failover guarantees, while non-critical services opportunistically use failover buffer capacity reserved for critical services during steady state. During rare "full-peak" failovers, non-critical services are selectively preempted and rapidly restored, with differentiated Service-Level Agreements (SLAs) using on-demand capacity. Automated safeguards, including dependency analysis and regression gates, ensure critical services continue to function even while non-critical services are unavailable. The quantitative impact is significant: UFA reduces steady-state provisioning from 2x to 1.3x, raising utilization from ~20% to ~30% while sustaining 99.97% availability. To date, UFA has hardened over 4,000 unsafe dependencies, eliminated over one million CPU cores from a baseline of about four million cores. |
| format | Preprint |
| id |
arxiv_https___arxiv_org_abs_2603_07345 |
| institution | arXiv |
| publishDate | 2026 |
| record_format | arxiv |
| spellingShingle | Uber's Failover Architecture: Reconciling Reliability and Efficiency in Hyperscale Microservice Infrastructure Bansal, Mayank Chabbi, Milind Bogh, Kenneth Prodduturi, Srikanth Xu, Kevin Kumar, Amit Bell, David Dey, Ranjib Ren, Yufei Sharma, Sachin Marcano, Juan Kale, Shriniket Pradhan, Subhav Beschastnikh, Ivan Covarrubias, Miguel Liao, Chien-Chih Sheshadri, Sandeep Koushik Luo, Wen Song, Kai Samant, Ashish Rihan, Sahil Sheth, Nimish Medisetty, Uday Kiran Distributed, Parallel, and Cluster Computing Networking and Internet Architecture Operating a global, real-time platform at Uber's scale requires infrastructure that is both resilient and cost-efficient. Historically, reliability was ensured through a costly 2x capacity model--each service provisioned to handle global traffic independently across two regions--leaving half the fleet idle. We present Uber's Failover Architecture (UFA), which replaces the uniform 2x model with a differentiated architecture aligned to business criticality. Critical services retain failover guarantees, while non-critical services opportunistically use failover buffer capacity reserved for critical services during steady state. During rare "full-peak" failovers, non-critical services are selectively preempted and rapidly restored, with differentiated Service-Level Agreements (SLAs) using on-demand capacity. Automated safeguards, including dependency analysis and regression gates, ensure critical services continue to function even while non-critical services are unavailable. The quantitative impact is significant: UFA reduces steady-state provisioning from 2x to 1.3x, raising utilization from ~20% to ~30% while sustaining 99.97% availability. To date, UFA has hardened over 4,000 unsafe dependencies, eliminated over one million CPU cores from a baseline of about four million cores. |
| title | Uber's Failover Architecture: Reconciling Reliability and Efficiency in Hyperscale Microservice Infrastructure |
| topic | Distributed, Parallel, and Cluster Computing Networking and Internet Architecture |
| url | https://arxiv.org/abs/2603.07345 |