[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2024-12-30。"],[[["\u003cp\u003eThis principle guides the establishment of achievable reliability goals for Google Cloud workloads, focusing on the scoping aspect of reliability within the Google Cloud Well-Architected Framework.\u003c/p\u003e\n"],["\u003cp\u003eStriving for 100% reliability may not be the most effective strategy, as it can lead to increased costs and limited innovation, recommending instead to determine sufficient reliability for user satisfaction.\u003c/p\u003e\n"],["\u003cp\u003eDetermining the level of reliability where users are satisfied helps allocate resources strategically to areas that will provide a higher value to the user.\u003c/p\u003e\n"],["\u003cp\u003eAccepting that some failures are inevitable and adopting an error budget allows for innovation and risk-taking, key for business competitiveness, while also prioritizing the reliability of critical components over less crucial ones.\u003c/p\u003e\n"],["\u003cp\u003eBalancing the reliability and the cost, organizations should determine the acceptable reliability level within the budget, considering factors such as system requirements, failure consequences, and disaster recovery metrics.\u003c/p\u003e\n"]]],[],null,["# Set realistic targets for reliability\n\nThis principle in the reliability pillar of the\n[Google Cloud Well-Architected Framework](/architecture/framework)\nhelps you define reliability goals that are technically feasible for your\nworkloads in Google Cloud.\n\nThis principle is relevant to the *scoping*\n[focus area](/architecture/framework/reliability#focus-areas)\nof reliability.\n\nPrinciple overview\n------------------\n\nDesign your systems to be just reliable enough for user happiness. It might\nseem counterintuitive, but a goal of 100% reliability is often not the most\neffective strategy. Higher reliability might result in a significantly higher\ncost, both in terms of financial investment and potential limitations on\ninnovation. If users are already happy with the current level of service, then\nefforts to further increase happiness might yield a low return on investment.\nInstead, you can better spend resources elsewhere.\n\nYou need to determine the level of reliability at which your users are happy,\nand determine the point where the cost of incremental improvements begin to\noutweigh the benefits. When you determine this level of *sufficient\nreliability*, you can allocate resources strategically and focus on features and\nimprovements that deliver greater value to your users.\n\nRecommendations\n---------------\n\nTo set realistic reliability targets, consider the recommendations in the\nfollowing subsections.\n\n### Accept some failure and prioritize components\n\nAim for high availability such as 99.99% uptime, but don't set a target of 100%\nuptime. Acknowledge that some failures are inevitable.\n\nThe gap between 100% uptime and a 99.99% target is the allowance for failure.\nThis gap is often called the *error budget*. The error budget can help you take\nrisks and innovate, which is fundamental to any business to stay competitive.\n\nPrioritize the reliability of the most critical components in the system.\nAccept that less critical components can have a higher tolerance for failure.\n\n### Balance reliability and cost\n\nTo determine the optimal reliability level for your system, conduct thorough\ncost-benefit analyses.\n\nConsider factors like system requirements, the consequences of failures, and\nyour organization's risk tolerance for the specific application. Remember to\nconsider your\n[disaster recovery metrics](/architecture/dr-scenarios-planning-guide#basics_of_dr_planning),\nsuch as the recovery time objective (RTO) and recovery point objective (RPO).\nDecide what level of reliability is acceptable within the budget and other\nconstraints.\n\nLook for ways to improve efficiency and reduce costs without compromising\nessential reliability features."]]
