知识卡片
工作流可见性按需设计
协同工作流没有天然中央进度表。可订阅相关输出流并物化状态,但观察范围应由问题决定:客户只需付款、履约、发货等里程碑,排障可能需要全部步骤。全链路监控越细,订阅数、数据量和变更成本越高;应明确哪些流程必须观察,避免把所有内部事件都公开成稳定接口。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Building Workflows with Microservices · 查看原书依据
When monitoring a choreographed workflow, you need to take into account its scale and scope. In isolation, distributed choreographed workflows can make it difficult to discern the processing progress of a specific event. For event-driven systems, monitoring business-critical workflows may necessitate listening to each output event stream and materializing it into a state store, to account for where an event may have failed to process or have gotten stuck in
参考来源
- 位置:《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;规范化段落起句:When monitoring a choreographed workflow)
- 结论依据:原文对该对象的定义、运行说明或对比支持以下归纳:协同工作流没有天然中央进度表。本卡同时保留其适用条件与失败边界。
- 原始内容:When monitoring a choreographed workflow, you need to take into account its scale and scope. In isolation, distributed choreographed workflows can make it difficult to discern the processing progress of a specific event. For event-driven systems, monitoring business-critical workflows may necessitate listening to each output event stream and materializing it into a state store, to account for where an event may have failed to process or have gotten stuck in