知识卡片
架构边界集中业务逻辑
架构模式组织输入输出、业务逻辑和基础设施之间的职责与依赖,防止规则散落于界面、数据库或多个入口。边界清楚后,业务变化所影响的代码更容易定位,也减少漏改和意外连带影响。选架构要服务业务逻辑的实现与维护,不能只按技术偏好选层数。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 架构模式 · 查看原书依据
Architectural patterns introduce organizational principles for the different aspects of a codebase and present clear boundaries between them: how the business logic is wired to the system’s input, output, and other infrastructural components. This affects how these components interact with each other: what knowledge they share and how the components reference each other. Choosing the
参考来源
- 位置:《Learning Domain-Driven Design》第8章《架构模式》(来源项目:book-sources;源文件:extracted/Learning Domain-Driven Design/_epub-src/OEBPS/ch08.html)
- 结论依据:原文围绕本卡所述机制给出定义、适用条件及相关取舍,以下摘录为直接依据。
- 原始内容:Architectural patterns introduce organizational principles for the different aspects of a codebase and present clear boundaries between them: how the business logic is wired to the system’s input, output, and other infrastructural components. This affects how these components interact with each other: what knowledge they share and how the components reference each other. Choosing the