知识卡片
能力部署与启用应分开
部署一套网格可先只启用所需能力,安装完成不代表所有策略已经运行或产生收益。采用计划应分别记录组件是否存在、功能是否开启及实际效果,避免把技术可用性当作目标已达成。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 渐进采用与演进架构 · 查看原书依据
Presence of a service mesh’s capabilities is separate from whether those capabilities are actively engaged. It’s been my experience that observability rises to the top of why most organizations initially deploy a service mesh. Outside of metrics, logs, and traces, typically you get a service dependency graph. These graphs visually identify how much traffic is coming from one service and going to the next. Without a visual topology or service
参考来源
- 位置:《The Enterprise Path to Service Mesh Architectures, 2nd Edition》第03章《渐进采用与演进架构》(来源项目book-sources;源文件:extracted/The Enterprise Path to Service Mesh Architectures, 2nd Edition/_epub-src/OEBPS/ch03.xhtml)
- 结论依据:原文在此说明该机制、范围或取舍;本卡保留其历史语境,不将预测、产品状态或命令作为当前已核验事实。
- 原始内容:Presence of a service mesh’s capabilities is separate from whether those capabilities are actively engaged. It’s been my experience that observability rises to the top of why most organizations initially deploy a service mesh. Outside of metrics, logs, and traces, typically you get a service dependency graph. These graphs visually identify how much traffic is coming from one service and going to the next. Without a visual topology or service