知识卡片
隔离不能依赖代码自律
即使各租户使用独立数据库,持有全局权限的服务仍可能因代码错误访问别人的数据库。隔离层应根据可信租户上下文限制资源访问,使错误查询也被拒绝;把开发团队视为可信不能替代对无意错误的技术约束。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Tenant Isolation · 查看原书依据
presume your code won’t break your isolation rules. Even the most careful and well-intended developers can unintentionally introduce changes that could end up crossing a tenant boundary. The industry is littered with examples of solutions that somehow exposed one tenant’s data to another tenant. Even a single instance of cross-tenant access could represent a significant setback for a SaaS business.
参考来源
- 位置:《Building Multi-Tenant SaaS Architectures》第09章《Tenant Isolation》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Multi-Tenant SaaS Architectures/_epub-src/OEBPS/ch09.html)
- 结论依据:原文具体说明即使各租户使用独立数据库,持有全局权限的服务仍可能因代码错误访问别人的数据库;本卡据此归纳机制及适用边界。
- 原始内容:presume your code won’t break your isolation rules. Even the most careful and well-intended developers can unintentionally introduce changes that could end up crossing a tenant boundary. The industry is littered with examples of solutions that somehow exposed one tenant’s data to another tenant. Even a single instance of cross-tenant access could represent a significant setback for a SaaS business.