知识卡片
专用资源不自动隔离
分开存放租户数据或为其建立专用计算资源,不等于已经阻止跨租户访问。同一服务若仍持有访问各租户资源的能力,就需要额外的策略或约束。隔离关注能否越过边界,资源部署形态只能影响实施难度。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Multi-Tenant Architecture Fundamentals · 查看原书依据
This holds true even with my separate databases. Nothing about putting the data in a separate database guarantees that tenants can’t cross this boundary. Generally, deploying a resource in a dedicated model doesn’t equate to achieving tenant isolation. It can make it easier to implement, though.
参考来源
- 位置:《Building Multi-Tenant SaaS Architectures》第02章《Multi-Tenant Architecture Fundamentals》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Multi-Tenant SaaS Architectures/_epub-src/OEBPS/ch02.html)
- 结论依据:原文具体说明分开存放租户数据或为其建立专用计算资源,不等于已经阻止跨租户访问;本卡据此归纳机制及适用边界。
- 原始内容:This holds true even with my separate databases. Nothing about putting the data in a separate database guarantees that tenants can’t cross this boundary. Generally, deploying a resource in a dedicated model doesn’t equate to achieving tenant isolation. It can make it easier to implement, though.