Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Even then, you do want to provide some degree of hardware-adjacent isolation to limit not just the blast radius but also computational cost of some DDL operations in a multi-tenant setup.

For example, you generally only want to have one tenant’s data per storage page. There are many famous ways that interleaving different tenants’ data at a fine-grained level can go very wrong.



Aggregating all tenants into the same tables could provide you with much more robust statistics for the query planner to use.

There are also advantages from a cache utilization standpoint if the system is heavily loaded.


Having tenants in the same tables is compatible with their data being on separate pages.


I am arguing for the I/O benefit of sharing pages between tenants.

I understand there are potential regulatory concerns with this, but I've never seen an audit get even remotely close to this level of detail.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: