知识卡片
客户端Sidecar会重新耦合
透明 sidecar 不要求业务代码显式调用;客户端式 sidecar 则需驱动库。驱动若带来大量依赖,会重新形成二进制耦合,同时还增加 sidecar 的可用性和运维成本。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第4章《Anti-Patterns: Internal Shared Libraries》(源文件:`_epub-src/OPS/ch04.xhtml`,归一化正文 [66977:71185))
- 结论依据:原文指出客户端式 sidecar 需要驱动,并列出驱动依赖、可靠性路径与额外复杂度等限制。
- 原始内容:The risk is all about the Sidecar driver; if the driver is lean and has fewer dependencies, we are good. For Client/Server sidecars, consider the following limitations and drawbacks: Drivers might be required : You might need to write drivers for multiple languages. Reliability path : The Sidecar needs to be always up and running; otherwise it will affect the reliability path of the service. Complexity : Some extra complexity, similar to a service approach.