知识卡片
监听与Lag触发的职责
监听器触发通常先替函数消费批次,函数专注处理;lag触发先启动函数,再由函数建立连接、消费并提交进度。定时、webhook和资源事件也可触发,但职责不同。批次大小和等待窗口摊销启动开销,同时增加等待;选择时看延迟、确认边界和所有权,不能只比较触发速度。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Microservices Using Function-as-a-Service · 查看原书依据
One of the major differences between the previously mentioned event-stream listener trigger and this one is that with lag triggering, the function does not consume the events until after it is started. Functions started by the lag trigger have a wider domain of responsibilities, including establishing a client connection with the event broker, consuming the events, and committing back any offset updates. This makes functions triggered by lag much more
参考来源
- 位置:《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 of the major differences between)
- 结论依据:原文对该对象的定义、运行说明或对比支持以下归纳:监听器触发通常先替函数消费批次,函数专注处理;lag触发先启动函数,再由函数建立连接、消费并提交进度。本卡同时保留其适用条件与失败边界。
- 原始内容:One of the major differences between the previously mentioned event-stream listener trigger and this one is that with lag triggering, the function does not consume the events until after it is started. Functions started by the lag trigger have a wider domain of responsibilities, including establishing a client connection with the event broker, consuming the events, and committing back any offset updates. This makes functions triggered by lag much more