知识卡片
函数提交时机决定保证
函数成功完成后提交offset可保留至少一次重试机会;开始执行或交接批次就提交,则业务失败后须依赖另一路重试和死信恢复,否则会丢处理。批次内部不能无条件吞错后统一宣告成功。应核验平台对重试、部分批次和确认的真实语义,函数被调用与业务完成是不同结果。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Microservices Using Function-as-a-Service · 查看原书依据
Offsets are committed at one of two times: when the function starts or when the function has completed its processing. Committing offsets only after processing has completed for a given event or batch of events is a FaaS best practice. It is important for you to understand how offsets for your specific function-based solutions are handled, so let’s take a look at the implications of each approach.
参考来源
- 位置:《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;规范化段落起句:Committing offsets only after processing)
- 结论依据:原文对该对象的定义、运行说明或对比支持以下归纳:函数成功完成后提交offset可保留至少一次重试机会;开始执行或交接批次就提交,则业务失败后须依赖另一路重试和死信恢复,否则会丢处理。本卡同时保留其适用条件与失败边界。
- 原始内容:Offsets are committed at one of two times: when the function starts or when the function has completed its processing. Committing offsets only after processing has completed for a given event or batch of events is a FaaS best practice. It is important for you to understand how offsets for your specific function-based solutions are handled, so let’s take a look at the implications of each approach.