知识卡片
边车复用运维能力
边车把监控、日志、服务发现和鉴权等运维能力从领域逻辑旁分离,每个服务附带一致实现;这些边车连接后形成网格,提供统一控制面。它让按领域划分的服务共享横切技术能力,而不必共享客户、地址等领域模型。代价是多平台适配和边车膨胀,应以适应度检查保证所有服务确实接入。
结构图:
flowchart LR
A[服务甲领域逻辑] --- B[甲的边车]
C[服务乙领域逻辑] --- D[乙的边车]
B <-->|统一运维能力| D
B --- E[统一监控与治理]
D --- E
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 复用模式 · 查看原书依据
If architects desire consistency in operational capabilities, the separable parts go into a sidecar component, metaphorically named for the sidecar that attaches to motorcycles, whose implementation is either a shared responsibility across teams or managed by a centralized infrastructure group. If architects can assume that every service includes the sidecar, it forms a consistent operational interface across services, typically attached via a service plane, shown in Figure 8-14.
参考来源
- 位置:《Software Architecture: The Hard Parts》第08章《复用模式》(来源项目:book-sources;源文件:extracted/Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)/_epub-src/OEBPS/ch08.xhtml)
- 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。
- 原始内容:If architects desire consistency in operational capabilities, the separable parts go into a sidecar component, metaphorically named for the sidecar that attaches to motorcycles, whose implementation is either a shared responsibility across teams or managed by a centralized infrastructure group. If architects can assume that every service includes the sidecar, it forms a consistent operational interface across services, typically attached via a service plane, shown in Figure 8-14.