知识卡片
组件隔离不必独立部署
工单分配失败路由后还需重新选专家,两种活动在运行上紧密绑定且负载一致。合成一个服务可减少协调和故障窗口;在服务内部再用不同命名空间分开分配、路由和共享代码,仍能保持维护边界。独立代码结构与独立部署不是同一个选择。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 服务粒度 · 查看原书依据
in that case, how about we make three distinct architectural components in the single service. We can delineate assignment, routing, and shared code with separate namespaces in the code. Would that help?
参考来源
- 位置:《Software Architecture: The Hard Parts》第07章《服务粒度》(来源项目: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/ch07.xhtml)
- 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。
- 原始内容:in that case, how about we make three distinct architectural components in the single service. We can delineate assignment, routing, and shared code with separate namespaces in the code. Would that help?