知识卡片
服务间治理按需求选型
服务间通信可由语言库处理,也可交给服务网格。单一语言、简单路由通常先用现有库;多语言且需统一认证、限流等横切能力时,网格更有价值。决策要核对当前约束和近期需求,同时计入网格运行成本。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- · 查看原书依据
If your organization mandates the use of a single programming language or framework, you can typically take advantage of the language-specific libraries or mechanisms for service-to-service communication. Always use the simplest solution for your requirements, with an eye to the immediate future and known requirements. If you have advanced cross-functional requirements, particularly across services that use different programming languages or technology stacks, a service mesh may be the best choice.
参考来源
- 位置:《Mastering API Architecture》第4章《Service Mesh: Service-to-Service Traffic Management》之《Guideline: Should You Adopt Service Mesh?》(源文件:_epub-src/OEBPS/ch04.xhtml)
- 结论依据:原文 ADR 指南按语言、路由复杂度、横切要求和组织既有组件比较库与网格,建议使用满足需求的最简方案。
- 原始内容:If your organization mandates the use of a single programming language or framework, you can typically take advantage of the language-specific libraries or mechanisms for service-to-service communication. Always use the simplest solution for your requirements, with an eye to the immediate future and known requirements. If you have advanced cross-functional requirements, particularly across services that use different programming languages or technology stacks, a service mesh may be the best choice.