知识卡片
异步通信减少同时在线要求
请求—响应让调用者等待特定接收方及时回复,适合需要即时结果的交互,也形成时间耦合。通过消息中介发布事件,接收方可在准备好后处理,并可能有多个订阅者。它把等待转移为队列与结果跟踪责任;是否真能容忍离线,还取决于保存、确认和重投的具体保证。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Loose Coupling · 查看原书依据
Systems using this request-response messaging pattern implicitly assume that a service is present and ready to promptly respond. But if it’s not, the request will fail. It can be said that they’re coupled in time. Coupling in time isn’t necessarily bad practice, though. It might even be preferable, particularly when there’s a human waiting for
参考来源
- 位置:《Cloud Native Go》第08章《Loose Coupling》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch08.xhtml)
- 结论依据:请求—响应让调用者等待特定接收方及时回复,适合需要即时结果的交互,也形成时间耦合。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。
- 原始内容:Systems using this request-response messaging pattern implicitly assume that a service is present and ready to promptly respond. But if it’s not, the request will fail. It can be said that they’re coupled in time. Coupling in time isn’t necessarily bad practice, though. It might even be preferable, particularly when there’s a human waiting for