知识卡片
内部调用避免绕行入口网关
让内部服务调用先离开内部网络、再经公开入口网关返回,会增加延迟、费用和安全风险,并使网关成为服务间通信瓶颈。外部请求继续走入口;内部调用应通过内部服务发现定位目标,保持内部链路在内部网络。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- · 查看原书依据
Often the first approach is to route all requests back through the publicly addressable gateway (e.g., the legacy application makes calls to www.conferencesystems.com/attendees). Instead, the legacy application should use some form of internal service discovery mechanism and keep all of the internal requests within the internal network. You will learn more about how to use a service mesh to implement this in the next chapter.
参考来源
- 位置:《Mastering API Architecture》第3章《API Gateways: Ingress Traffic Management》之《API Gateway Loopback》(源文件:_epub-src/OEBPS/ch03.xhtml)
- 结论依据:原文指出回环入口网关造成性能、安全、费用和单点问题,并明确建议内部应用使用内部服务发现。
- 原始内容:Often the first approach is to route all requests back through the publicly addressable gateway (e.g., the legacy application makes calls to www.conferencesystems.com/attendees ). Instead, the legacy application should use some form of internal service discovery mechanism and keep all of the internal requests within the internal network. You will learn more about how to use a service mesh to implement this in the next chapter.