知识卡片
重建与迁移状态的取舍
重建从足够完整的输入按新业务逻辑生成状态,减少独立迁移逻辑,却要承担耗时、输入保留和重复输出影响。迁移直接修改现有数据,适合简单结构变化或仅影响未来数据的需求;复杂迁移可能与完整重建结果不一致。应用代表性数据比较两条路径,并将恢复耗时纳入SLA,不能只比较执行脚本的速度。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Stateful Streaming · 查看原书依据
Rebuilding the microservice’s state stores is typically the most common method of updating the internal state of an application. The microservice is first stopped, with the consumer input stream offsets reset to the beginning. Any intermediate state, such as that stored in a changelog or located in the external state store, must be deleted. Lastly, the new version of the microservice is started up, and the state is rebuilt as
参考来源
- 位置:《Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)》第07章《Stateful Streaming》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)/_epub-src/OEBPS/ch07.xhtml;规范化段落起句:Rebuilding the microservice’s state stores)
- 结论依据:原文对该对象的定义、运行说明或对比支持以下归纳:重建从足够完整的输入按新业务逻辑生成状态,减少独立迁移逻辑,却要承担耗时、输入保留和重复输出影响。本卡同时保留其适用条件与失败边界。
- 原始内容:Rebuilding the microservice’s state stores is typically the most common method of updating the internal state of an application. The microservice is first stopped, with the consumer input stream offsets reset to the beginning. Any intermediate state, such as that stored in a changelog or located in the external state store, must be deleted. Lastly, the new version of the microservice is started up, and the state is rebuilt as