知识卡片
共享版本可能绑住独立部署
若服务必须使用同一内部库及版本才能启动或通信,升级就可能变成全系统同步动作。它们虽分成多个进程,却失去独立发布优势,形成分布式单体。共享代码本身不是错误,风险在把变化频繁的实现细节变成全系统契约。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Loose Coupling · 查看原书依据
services were required to use specific libraries — and versions of libraries — in order to launch and interact with one another. Such systems find themselves saddled with a fleet-wide dependency, such that upgrading these shared libraries can force all services to have to upgrade in lockstep. As we’ll discuss in “Distributed Monoliths”, this isn’t
参考来源
- 位置:《Cloud Native Go》第08章《Loose Coupling》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch08.xhtml)
- 结论依据:若服务必须使用同一内部库及版本才能启动或通信,升级就可能变成全系统同步动作。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。
- 原始内容:services were required to use specific libraries — and versions of libraries — in order to launch and interact with one another. Such systems find themselves saddled with a fleet-wide dependency, such that upgrading these shared libraries can force all services to have to upgrade in lockstep. As we’ll discuss in “Distributed Monoliths”, this isn’t