知识卡片
边车降低局部故障范围
每个应用配套代理,便于把资源和身份归到服务,也可把代理故障范围限制在该应用。与节点共享代理相比,隔离更细,但每服务都支付代理资源开销,应结合服务密度评估。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 渐进采用与演进架构 · 查看原书依据
App-to-sidecar communication easier to secure than app-to-node proxy Resources consumed for a service are attributed to that service Blast radius of a proxy failure limited to the sidecarred app Disadvantages Sidecar footprint—per service overhead of running a service proxy sidecar Multicluster and Cross-Cluster Deployments Some service meshes support deployment across Kubernetes clusters. Istio multicluster deployments facilitate connections between service proxies (Envoys) running in different clusters to one Istio control plane
参考来源
- 位置:《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)
- 结论依据:原文在此说明该机制、范围或取舍;本卡保留其历史语境,不将预测、产品状态或命令作为当前已核验事实。
- 原始内容:App-to-sidecar communication easier to secure than app-to-node proxy Resources consumed for a service are attributed to that service Blast radius of a proxy failure limited to the sidecarred app Disadvantages Sidecar footprint—per service overhead of running a service proxy sidecar Multicluster and Cross-Cluster Deployments Some service meshes support deployment across Kubernetes clusters. Istio multicluster deployments facilitate connections between service proxies (Envoys) running in different clusters to one Istio control plane