知识卡片
BPM保留流程状态
业务流程管理适合跨应用、可中断、可能等待人工的长流程,记录任务、规则、状态与等待关系。客户、合同等业务实体仍应由相应应用管理,不能把流程引擎当成共享业务数据库。短小域内流程也未必需要独立BPM平台。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Services and API Management · 查看原书依据
The process layer of the BPM software holds all the information about the data exchange flow between applications and services: the sequence information, dependencies, status, tasks, rules, waiting times, etc. You should never store application data in such a process layer; this is a common mistake. BPM software isn’t meant for managing application data. Use the BPM API to start processes and retrieve information about
参考来源
- 位置:《Data Management at Scale》第05章《Services and API Management》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch05.html)
- 结论依据:原文对should never store application data的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。
- 原始内容:The process layer of the BPM software holds all the information about the data exchange flow between applications and services: the sequence information, dependencies, status, tasks, rules, waiting times, etc. You should never store application data in such a process layer; this is a common mistake. BPM software isn’t meant for managing application data. Use the BPM API to start processes and retrieve information about