知识卡片
编排器只拥有流程逻辑
编排器拥有步骤顺序、分支和进度,工作服务拥有具体业务执行与内部重试。支付服务应自己完成约定的支付尝试再返回最终结果,而非让编排器逐次指挥底层操作。边界清楚可集中修改流程又保持业务封装;若大量细粒度命令把逻辑拆在两边,会形成上帝服务和无自治的从属服务。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Building Workflows with Microservices · 查看原书依据
Ensure the orchestrator’s bounded context is limited strictly to workflow logic and that it contains minimal business fulfillment logic. The orchestrator contains only the workflow logic, while the services under orchestration contain the bulk of the business logic.
参考来源
- 位置:《Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)》第08章《Building Workflows with Microservices》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)/_epub-src/OEBPS/ch08.xhtml;规范化段落起句:Ensure the orchestrator’s bounded context)
- 结论依据:原文对该对象的定义、运行说明或对比支持以下归纳:编排器拥有步骤顺序、分支和进度,工作服务拥有具体业务执行与内部重试。本卡同时保留其适用条件与失败边界。
- 原始内容:Ensure the orchestrator’s bounded context is limited strictly to workflow logic and that it contains minimal business fulfillment logic. The orchestrator contains only the workflow logic, while the services under orchestration contain the bulk of the business logic.