Hyperforce上高可用性的架构原则

Infrastructure and software failures will happen. We idolize four 9s (99.99%) availability. We know we need to optimize and improve Recovery-Time-Objective (RTO, the time it takes to restore service after a service disruption) and Recovery-Point-Objective (RPO, the acceptable data loss measured in time). But how can we actually deliver high availability for our customers?

基础设施和软件故障会发生。我们推崇四个9（99.99%）的可用性。我们知道我们需要优化和改善恢复时间目标（RTO，在服务中断后恢复服务所需的时间）和恢复点目标（RPO，以时间衡量可接受的数据损失）。但是，我们如何才能真正为我们的客户提供高可用性？

One of the missions of Salesforce’s engineering team is to prevent and minimize service disruptions. To achieve high availability for our customers, we design cloud-native architectural solutions that enable resilience for infrastructure failures and faster resolutions for unplanned incidents. We adopt safe deployment for non-disruptive software updates and releases.

Salesforce工程团队的任务之一是防止和减少服务中断。为了给客户实现高可用性，我们设计了云原生架构解决方案，以实现对基础设施故障的恢复能力，并更快地解决计划外的事件。我们采用安全部署，以实现无中断的软件更新和发布。

This post will share our architectural principles for high availability that we’ve learned over the years and are applying to the Salesforce Hyperforce platform.

这篇文章将分享我们多年来学到的高可用性的架构原则，并将其应用于SalesforceHyperforce平台。

High Availability Architectural Principles

高可用性架构原则

1. Build your services on infrastructure across multiple fault domains2. Adopt a safe deployment strategy3. Understand your “Blast Radius” and minimize it4. Take advantage of the elastic capacity5. Design to withstand dependency failures

1.在跨越多个故障域的基础设施上构建你的服务2。采用安全的部署策略3。了解你的 "爆炸半径 "并将其最小化4。利用弹性容量的优势5。设计时要经得起依赖性故障的考验

6. Measure, learn, and improve continuously

6.衡量、学习和持续改进

1. Build your services on infrastructure across multiple fault domains

1.在跨越多个故障域的基础设施上构建你的服务

Salesforce Hyperforce is built natively on public cloud infrastructure. The public cloud providers operate multiple data centers in a single region. Data centers are grouped into “availability zones” (AZ) in distinct physical locations with independent power and networks to prevent correlated infrastructure failures. The availabil...