知识卡片
协调服务要防阻塞累积
独立协调服务接收一次用户请求,再在数据中心内调用其他服务,适合数秒内结束的简单流程。它比客户端多轮往返容易控制可信业务逻辑,但大量网络等待可能耗尽每请求一线程模型的资源。非阻塞异步可改善并发,却提高实现复杂度,应把团队经验纳入选择,而非默认“多一个服务”就高效。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 宏观架构中的协调 · 查看原书依据
The primary disadvantage of using another service for coordination is that a lot depends on the performance of the service. Because the coordination service makes many service calls, the simplest server architectures such as the thread-per-request model do not provide good performance, and implementing a nonblocking asynchronous style service is complicated. If you choose to write code to do asynchronous calls, make sure you have a few team members who have done it before.
参考来源
- 位置:《Software Architecture and Decision-Making》第06章《宏观架构中的协调》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch06.xhtml)
- 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。
- 原始内容:The primary disadvantage of using another service for coordination is that a lot depends on the performance of the service. Because the coordination service makes many service calls, the simplest server architectures such as the thread-per-request model do not provide good performance, and implementing a nonblocking asynchronous style service is complicated. If you choose to write code to do asynchronous calls, make sure you have a few team members who have done it before.