← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 2275.as.6.f.3.c.1.e.2.d.2.a

顺序保证有分区范围

理解等级:高级

事件可能乱序,消费时需明确顺序的业务键、分区范围和序号。分区内有序不代表所有分区存在统一全局顺序;增加并行分区会改变协调需求。若在消费侧重排,应同时处理缺失、重复和等待窗口。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Event and Notification Management · 查看原书依据

      Another typical challenge with streaming is the message order. In some cases messages are required to be strictly ordered, for example, by order of creation. Kafka allows you to do this, but only using one partition. If you need more partitions for scalability, the ordering must be based on an additional property in the message, such as the row_no. This might require the delivering party

    参考来源

    - 位置:《Data Management at Scale》第06章《Event and Notification Management》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch06.html) - 结论依据:原文对only using one partition的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。 - 原始内容:Another typical challenge with streaming is the message order. In some cases messages are required to be strictly ordered, for example, by order of creation. Kafka allows you to do this, but only using one partition. If you need more partitions for scalability, the ordering must be based on an additional property in the message, such as the row_no. This might require the delivering party