知识卡片
配置权威来源须明确
不同监控、目录和服务发现工具常有自己的专用注册表,强迫它们全部接入统一注册表,会使每次工具升级都伴随集成维护。可以保留多个注册表,明确每项配置的权威来源,再按需汇集数据或发送变更事件;集中查看不等于集中拥有。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 配置基础设施栈实例 · 查看原书依据
Combining all configuration values from across all your systems, services, and tools is an appealing idea. You could keep everything in one place rather than sprawling across many systems. “One registry to rule them all.” However, this isn’t always practical in larger, more heterogeneous environments. Many tools, such as monitoring services and server configuration systems,
参考来源
- 位置:《Infrastructure As Code》第8章《配置基础设施栈实例》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch08.html)
- 结论依据:原文说明不同监控、目录和服务发现工具常有自己的专用注册表,强迫它们全部接入统一注册表,会使每次工具升级都伴随集成维护;本卡据此解释其用途及适用边界。
- 原始内容:Combining all configuration values from across all your systems, services, and tools is an appealing idea. You could keep everything in one place rather than sprawling across many systems. “One registry to rule them all.” However, this isn’t always practical in larger, more heterogeneous environments. Many tools, such as monitoring services and server configuration systems,