知识卡片
最少知识支持替换
消费者应依赖组件公开输出,而不是内部资源名称与结构。网络组件导出稳定的子网标识,消费方从这个接口发现资源,提供方即可改变内部子网布局。相同接口也能让测试使用轻量网络实现,生产使用完整实现;这要求约定的能力足够,而非假定所有网络实现天然可互换。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 基础设施代码设计原则 · 查看原书依据
A useful technique for making infrastructure components composable is to implement interfaces between them at the component level rather than integrating with specific IaaS resources in them. Figure 5-4 illustrates the difference. The components on the left have a dependency defined at the resource level. The code that defines the load balancer in the consumer
参考来源
- 位置:《Infrastructure As Code》第5章《基础设施代码设计原则》(来源项目 book-sources,源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch05.html)
- 结论依据:原文对该概念的定义、应用条件与作用机制直接支持上述解释。
- 原始内容:A useful technique for making infrastructure components composable is to implement interfaces between them at the component level rather than integrating with specific IaaS resources in them. Figure 5-4 illustrates the difference. The components on the left have a dependency defined at the resource level. The code that defines the load balancer in the consumer