← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 1980.z.6.b.1

事件与直调的编排取舍

理解等级:高级

同步编排在依赖健康时通常响应更快,但需要协调者处理连接、超时和恢复。事件编排通过代理保留命令与结果,缓冲双方短暂不可用,也可供其他消费者复用,代价是额外传递延迟和运行组件。可混用,但必须定义超时、重复命令和最终结果的含义,不能把异步请求响应误当成自动获得端到端事务。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Building Workflows with Microservices · 查看原书依据

      To summarize, direct-call aka synchronous request-response workflows are generally faster than event-driven ones, provided all dependent services are operating within their SLAs. They tend to work well when very quick responses are required, such as in real-time operations. Meanwhile, event-driven workflows have more durable I/O streams, producing slower but more robust operations, and are particularly good at handling intermittent failures.

    参考来源

    - 位置:《Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)》第08章《Building Workflows with Microservices》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)/_epub-src/OEBPS/ch08.xhtml;规范化段落起句:To summarize, direct-call aka synchronous) - 结论依据:原文对该对象的定义、运行说明或对比支持以下归纳:同步编排在依赖健康时通常响应更快,但需要协调者处理连接、超时和恢复。本卡同时保留其适用条件与失败边界。 - 原始内容:To summarize, direct-call aka synchronous request-response workflows are generally faster than event-driven ones, provided all dependent services are operating within their SLAs. They tend to work well when very quick responses are required, such as in real-time operations. Meanwhile, event-driven workflows have more durable I/O streams, producing slower but more robust operations, and are particularly good at handling intermittent failures.