知识卡片
拦截机制减少隔离漏用
切面、中间件或包装库可在请求入口统一取得受限权限,代理或sidecar则可在资源访问路径执行约束。两种方式减少依赖业务开发者手工调用,但都须检查覆盖范围、上下文可信性及可绕过路径,不能只看组件是否安装。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Tenant Isolation · 查看原书依据
from the isolation equation as much as possible. The more you need to rely on developers as part of the isolation story, the more cumbersome and fragile your isolation becomes. This is where teams will often look for opportunities to introduce interception mechanisms that can enforce isolation without relying heavily on developers applying specific conventions and constructs within the body
参考来源
- 位置:《Building Multi-Tenant SaaS Architectures》第09章《Tenant Isolation》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Multi-Tenant SaaS Architectures/_epub-src/OEBPS/ch09.html)
- 结论依据:原文具体说明切面、中间件或包装库可在请求入口统一取得受限权限,代理或sidecar则可在资源访问路径执行约束;本卡据此归纳机制及适用边界。
- 原始内容:from the isolation equation as much as possible. The more you need to rely on developers as part of the isolation story, the more cumbersome and fragile your isolation becomes. This is where teams will often look for opportunities to introduce interception mechanisms that can enforce isolation without relying heavily on developers applying specific conventions and constructs within the body