知识卡片
聚合编排有责任边界
服务聚合把多个接口组合成一个入口,编排则决定调用次序和结果组合。中央编排便于复用,却增加中心性能与故障依赖,还可能模糊底层责任;消费域编排更贴近自身业务逻辑,但会承担重复实现成本。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Services and API Management · 查看原书依据
Service aggregation requires service orchestration, the coordination and execution of tasks to combine and integrate different services.5 This is commonly done for technical reasons, such as combining, splitting, transforming, inspecting, and discarding data. The service orchestration process can be short-running, making fairly straightforward combinations, in cases where a simple service flow across services is needed.6 For example, in order to get all of a customer’s
参考来源
- 位置:《Data Management at Scale》第05章《Services and API Management》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch05.html)
- 结论依据:原文对coordination and execution of tasks的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。
- 原始内容:Service aggregation requires service orchestration, the coordination and execution of tasks to combine and integrate different services.5 This is commonly done for technical reasons, such as combining, splitting, transforming, inspecting, and discarding data. The service orchestration process can be short-running, making fairly straightforward combinations, in cases where a simple service flow across services is needed.6 For example, in order to get all of a customer’s