知识卡片
依赖倒置保留替换边界
高层业务依赖仓储等抽象契约,具体数据库实现适配契约,通过注入提供给业务。这样可隔离存储变化并便于测试;抽象仍须表达真实事务和失败语义,不能抹去不同后端的保证差异。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Design for Speed and Efficiency · 查看原书依据
The Dependency Inversion Principle (DIP) states that high-level modules should depend on abstractions, not on concrete implementations. In a serverless context, this principle can be applied by designing functions and microservices to depend on abstractions or interfaces rather than concrete implementations.
参考来源
- 位置:《Building Distributed Systems Designing scalable architectures with microservices, event-driven patterns, and robust deployment…》第05章《Design for Speed and Efficiency》(来源项目book-sources;源文件:extracted/Building Distributed Systems Designing scalable architectures with microservices, event-driven patterns, and robust deployment…/_epub-src/OPS/ch05.xhtml)
- 结论依据:原文的机制或对比支持以下核心判断:高层业务依赖仓储等抽象契约,具体数据库实现适配契约,通过注入提供给业务。 本卡将相邻说明中的适用限制保留为解释。
- 原始内容:The Dependency Inversion Principle (DIP) states that high-level modules should depend on abstractions, not on concrete implementations. In a serverless context, this principle can be applied by designing functions and microservices to depend on abstractions or interfaces rather than concrete implementations.