知识卡片
性能目标按负载与操作分域
“500毫秒内返回”只有结合负载、有效输入、响应种类和分位数才可验证。计算密集报价可能需要独立目标,不能硬套一般页面操作阈值;无效请求也可有快速拒绝要求。各范围须互相清楚,并区分单次同步响应与后续异步完成,避免照抄原例503与成功并列的含混语义。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Testable CFRs and Technology Strategy · 查看原书依据
This example is interesting because the CFR is making a big assumption. It’s assuming that all requests to the system have to process a similar workload and can therefore have a hope of responding “within 500 ms.” Think again of the example insurance broker SaaS (Organization Z in “You’re Aligned When You’re Not Surprised”).
参考来源
- 位置:《Facilitating Software Architecture》第09章《Testable CFRs and Technology Strategy》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch09.html)
- 结论依据:原文指出通用工作量假设不成立,增加报价及invalid request独立范围;数字仅为书内示例。
- 原始内容:This example is interesting because the CFR is making a big assumption. It’s assuming that all requests to the system have to process a similar workload and can therefore have a hope of responding “within 500 ms.” Think again of the example insurance broker SaaS (Organization Z in “You’re Aligned When You’re Not Surprised”).