知识卡片
函数串接的确认与顺序
函数A异步调用B后立即确认输入,B若失败而无耐久重试,A的offset已前进;多次并发B还可能乱序完成。内部事件流为每阶段提供可恢复消费边界,逐事件同步编排则可等A、B全部完成再确认,但会增加等待。需要同键顺序时必须保持明确执行所有权,不能因FaaS能无限并行就忽略业务顺序。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Microservices Using Function-as-a-Service · 查看原书依据
One major downside to asynchronous direct calls is in ensuring that the consumer offsets are updated only in the case of successful processing. In the example, function B has no feedback to function A, and so only errors in function A will prevent the workflow from incorrectly committing the consumer group offsets. However, losing events may not matter to some workflows, and in those cases this problem can be
参考来源
- 位置:《Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)》第09章《Microservices Using Function-as-a-Service》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)/_epub-src/OEBPS/ch09.xhtml;规范化段落起句:One major downside to asynchronous direct calls)
- 结论依据:原文对该对象的定义、运行说明或对比支持以下归纳:函数A异步调用B后立即确认输入,B若失败而无耐久重试,A的offset已前进;多次并发B还可能乱序完成。本卡同时保留其适用条件与失败边界。
- 原始内容:One major downside to asynchronous direct calls is in ensuring that the consumer offsets are updated only in the case of successful processing. In the example, function B has no feedback to function A, and so only errors in function A will prevent the workflow from incorrectly committing the consumer group offsets. However, losing events may not matter to some workflows, and in those cases this problem can be