知识卡片
Sidecar代理有数据访问代价
Sidecar若替服务发出数据库请求并应用受限凭证,就可能需要承载数据访问逻辑;若只把凭证返还服务,又更像外置辅助库。采用它前应明确业务与代理职责、绕过控制和协议实现成本,不能因代理位于路径中就假定其天然解决隔离。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- EKS (Kubernetes) SaaS: Architecture Patterns and Strategies · 查看原书依据
to the request. This would essentially mean that you would need to put a data access library in the sidecar to make this work. That may not be the best division of labor or how you want your microservice code distributed.
参考来源
- 位置:《Building Multi-Tenant SaaS Architectures》第10章《EKS (Kubernetes) SaaS: Architecture Patterns and Strategies》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Multi-Tenant SaaS Architectures/_epub-src/OEBPS/ch10.html)
- 结论依据:原文具体说明Sidecar若替服务发出数据库请求并应用受限凭证,就可能需要承载数据访问逻辑;若只把凭证返还服务,又更像外置辅助库;本卡据此归纳机制及适用边界。
- 原始内容:to the request. This would essentially mean that you would need to put a data access library in the sidecar to make this work. That may not be the best division of labor or how you want your microservice code distributed.