知识卡片

普通读书笔记卡 · 2285.f.12

按等待与边界拆任务

理解等级:中级

业务逻辑默认用普通代码实现;需要持久等待、经常与相关方讨论或跨越事务边界的部分适合进入模型。一个任务内调用两个服务,失败后引擎只能按整任务重试;拆成两个任务可记住第一个调用已完成,单独重试第二个。模型粒度决定恢复粒度。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 开发流程方案 · 查看原书依据

      The workflow engine enables this at the granularity of tasks. For instance, if the glue code attached to one task calls two remote services, you can only proceed if both calls are successful. But if you design two service tasks that make only one remote call each, the workflow engine can remember that one service call was already successfully executed and just retry the other.

    参考来源

    - 位置:《Practical Process Automation》第3章《开发流程方案》(来源项目:book-sources;源文件:extracted/Practical Process Automation (Bernd Ruecker)/_epub-src/OEBPS/ch03.xhtml) - 结论依据:原文中的定义、机制和适用条件支持上述解释,正文未将产品示例推广为所有引擎的保证。 - 原始内容:The workflow engine enables this at the granularity of tasks. For instance, if the glue code attached to one task calls two remote services, you can only proceed if both calls are successful. But if you design two service tasks that make only one remote call each, the workflow engine can remember that one service call was already successfully executed and just retry the other.