知识卡片
概念验证应比较实现代价
两个方案在纸面上都满足架构目标时,概念验证可把实现细节变成可比较的证据。原书以两种缓存产品为例:分别做可工作的样例,观察开发投入,并比较伸缩性、性能与容错性。
概念验证代码应尽量保持生产级质量,因为“临时”样例可能进入仓库并成为团队的参考实现。这是对代码可被复用的风险控制,并不意味着每个概念验证都已通过生产验收。可与[[架构师写代码应避开关键路径]]配合。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Architectural Thinking · 查看原书依据
One effective way to help make this decision is to develop a working example in each caching product and compare the results. This allows the architect to see firsthand the implementation details and the amount of effort required to develop the full solution.
参考来源
- 位置:《Fundamentals of Software Architecture》第04章《Architectural Thinking》(源文件:`OEBPS/ch02.html`,Balancing Architecture and Hands-On Coding → Frequent proofs-of-concept)
- 结论依据:原文用两个缓存产品的工作样例比较实现投入和架构特征,并说明临时代码可能成为参考架构;最后的生产验收边界为应用推断。
- 原始内容:One effective way to help make this decision is to develop a working example in each caching product and compare the results. This allows the architect to see firsthand the implementation details and the amount of effort required to develop the full solution.