Auto-sync: 2026-04-19 06:32
This commit is contained in:
30
wiki/concepts/NFR.md
Normal file
30
wiki/concepts/NFR.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
id: nfr
|
||||
title: "NFR(非功能需求)"
|
||||
type: concept
|
||||
tags: [sre, requirements, reliability]
|
||||
last_updated: 2026-04-19
|
||||
---
|
||||
|
||||
## Definition
|
||||
NFR(Non-Functional Requirements,非功能需求)是评判系统运行状况的标准,决定可用性、性能、安全性、可扩展性等属性。
|
||||
|
||||
## Key Aspects
|
||||
- **可用性(Availability)**:系统正常运行时间比例(如 99.9%、99.99%)
|
||||
- **性能(Performance)**:响应时间、吞吐量等
|
||||
- **安全性(Security)**:数据加密、访问控制等
|
||||
- **可扩展性(Scalability)**:水平/垂直扩展能力
|
||||
|
||||
## Cloud Context
|
||||
在云端,NFR 应更规范化,利用云原生服务:
|
||||
- AWS Backup 定义备份策略和测试频率
|
||||
- DR 规划包含季度测试和 IaC 基础设施
|
||||
- NFR Epic 集成到 Sprint backlog
|
||||
|
||||
## Relationship with SRE
|
||||
- [[SRE]] 通过 [[Error Budget(错误预算)]] 和 [[SLO(服务等级目标)]] 实现 NFR
|
||||
- [[混沌工程]] 验证 NFR 是否满足
|
||||
|
||||
## References
|
||||
- [[CTP Topic 41 NFR's and Error Budgets]] — NFR 在云和敏捷开发中的应用
|
||||
- [[Brendan Standing]] — Micro Focus SRE 负责人
|
||||
Reference in New Issue
Block a user