知识卡片
组件清单需要双向依赖
评估清单不能只列服务名;应记录所有者、业务变化率、公开契约、上游消费者、下游依赖、用户触点、测试状态和数据库读写关系。这些维度让组件处置决策可复核。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第5章《Assessments》(源文件:`_epub-src/OPS/ch05.xhtml`,归一化正文 [37759:41966))
- 结论依据:原文列出代码分析清单维度,包含组件、所有权、契约、上下游、用户、复杂度、测试与数据存储。
- 原始内容:List of downstream dependencies : List out downstream services or integrations. Who you gonna call? List of upstream dependencies : List all services or components that call you, ideally with the protocols and operations they are using. User facing : Do humans (consumers, employees, contractors) use this component directly? Or is it solely machine to machine communication, i.e. service calling service? Complexity : Describe the component’s solution complexity and obscurity. List known anti-patterns and technical debts.