知识卡片
架构约束要持续核验
架构决策写下后,还要持续核验团队实现是否遵守,否则系统可能失去原本要保障的质量属性。
原书例子:分层架构规定只有业务层和服务层能访问数据库,以隔离数据库变更对表示层的影响;若表示层为了性能直接访问数据库,就绕过了这项约束。
实践推断:若性能压力要求改变规则,应重新评估并记录取舍,不能靠无记录的违规实现替代决策。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Introduction · 查看原书依据
Ensuring compliance means continually verifying that the development teams are following the decisions and design principles defined, documented, and communicated by the architect. Imagine that you, as an architect, make a decision to restrict access to the database in a layered architecture to only the Business and Services layers (not the Presentation layer).
参考来源
- 位置:《Fundamentals of Software Architecture》第02章《Introduction》(源文件:`OEBPS/ch01.html`,Ensure Compliance with Decisions)
- 结论依据:正文定义持续核验架构决策的职责,并用表示层直接访问数据库说明违反层间规则会削弱原先的隔离目标;末句是基于该例的实践推断。
- 原始内容:Ensuring compliance means continually verifying that the development teams are following the decisions and design principles defined, documented, and communicated by the architect. Imagine that you, as an architect, make a decision to restrict access to the database in a layered architecture to only the Business and Services layers (not the Presentation layer).