知识卡片
消费处理与提交窗口
事件服务通常先消费、处理和输出,再提交消费offset。processEvent是业务拓扑入口,可产出零个或多个结果。提交前失败会重读已处理记录,因此示例只是至少一次处理,不能把代码执行完成当成业务副作用恰好一次。无状态只意味着无需历史状态完成当前计算,不意味着故障不会重复输出。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Event-Driven Processing Basics · 查看原书依据
The processEvent function is of particular interest. This is where the real event-processing work gets done, primarily the application of business logic and which events, if any, to emit. This processing function is best thought of as the entry point to the processing topology of the microservice. From here, data-driven patterns transform and process the data for your bounded context’s business needs.
参考来源
- 位置:《Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)》第05章《Event-Driven Processing Basics》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)/_epub-src/OEBPS/ch05.xhtml;规范化段落起句:The processEvent function is of particular)
- 结论依据:原文对该对象的定义、运行说明或对比支持以下归纳:事件服务通常先消费、处理和输出,再提交消费offset。本卡同时保留其适用条件与失败边界。
- 原始内容:The processEvent function is of particular interest. This is where the real event-processing work gets done, primarily the application of business logic and which events, if any, to emit. This processing function is best thought of as the entry point to the processing topology of the microservice. From here, data-driven patterns transform and process the data for your bounded context’s business needs.