知识卡片
编排者可能过度集中
协调者若不断吸收业务判断,依赖服务可能退化为只做数据增删改查的工具,协调者则变成难扩展、难测试的中心。判断边界时应区分工作流协调与领域规则,避免每次新增功能都向同一中心堆叠条件分支。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Monoliths and Microservices · 查看原书依据
Centralization of logic, in an orchestration model, the orchestrator holds the majority of the business logic, directing the flow of operations and making decisions. This centralization can create a bottleneck, as the orchestrator becomes a critical point of failure. If the orchestrator service fails, the entire system's workflow can be disrupted. These systems evolve into an all-knowing single brain. Its dependencies sometimes get reduced to
参考来源
- 位置:《Building Distributed Systems Designing scalable architectures with microservices, event-driven patterns, and robust deployment…》第02章《Monoliths and Microservices》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Distributed Systems Designing scalable architectures with microservices, event-driven patterns, and robust deployment…/_epub-src/OPS/ch02.xhtml)
- 结论依据:原文以服务职责、依赖或运行情境展开本卡主题;本卡保留其作用条件与代价,不把局部优势推广为无条件保证。
- 原始内容:Centralization of logic, in an orchestration model, the orchestrator holds the majority of the business logic, directing the flow of operations and making decisions. This centralization can create a bottleneck, as the orchestrator becomes a critical point of failure. If the orchestrator service fails, the entire system's workflow can be disrupted. These systems evolve into an all-knowing single brain. Its dependencies sometimes get reduced to