知识卡片
蓝绿输出必须隔离
独立组与状态让新版追赶输入后切同步流量,适合读服务的蓝绿部署。但若新旧两版消费相同事实并写同一输出流,可能重复事件或互相覆盖实体。不能仅复制进程再切HTTP就宣称事件处理无缝上线;有输出服务必须明确输出隔离、所有权交接和副作用策略,或采用适合的全停/滚动更新。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Deploying Event-Driven Microservices · 查看原书依据
Blue-green deployments do not work when the microservice produces events to an output stream in reaction to an input event stream. The two microservices will overwrite each other’s results in the case of entity streams or will create duplicated events in the case of event streams. Use either the rolling update pattern or the basic full-stop deployment pattern instead.
参考来源
- 位置:《Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)》第16章《Deploying Event-Driven Microservices》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)/_epub-src/OEBPS/ch16.xhtml;规范化段落起句:Blue-green deployments do not work)
- 结论依据:原文对该对象的定义、运行说明或对比支持以下归纳:独立组与状态让新版追赶输入后切同步流量,适合读服务的蓝绿部署。本卡同时保留其适用条件与失败边界。
- 原始内容:Blue-green deployments do not work when the microservice produces events to an output stream in reaction to an input event stream. The two microservices will overwrite each other’s results in the case of entity streams or will create duplicated events in the case of event streams. Use either the rolling update pattern or the basic full-stop deployment pattern instead.