知识卡片

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

总线不宜承担业务状态

理解等级:高级

如果ESB保存多个应用的业务状态,应用变更必须协调共享结构,中心故障也会影响多个流程。技术中介宜仅保留必要会话与缓存;业务实体归应用,长流程状态归明确的流程能力,避免状态责任混淆。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Services and API Management · 查看原书依据

      The last similarity I want to point out is that the ESB has become a state (data) store for multiple applications.8 Rather than taking care of the state in the application or a business process management capability, the ESB is used to orchestrate long-running business processes or, even worse, to persist the state that belongs to applications. The ESB becomes a database. The risk of

    参考来源

    - 位置:《Data Management at Scale》第05章《Services and API Management》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch05.html) - 结论依据:原文对ESB, in principle, should be stateless的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。 - 原始内容:The last similarity I want to point out is that the ESB has become a state (data) store for multiple applications.8 Rather than taking care of the state in the application or a business process management capability, the ESB is used to orchestrate long-running business processes or, even worse, to persist the state that belongs to applications. The ESB becomes a database. The risk of