Multi-tenant Design Approach
I am working on a project that involves an organization signing up and then multiple customers will be signing in per organization. I want to introduce multi-tenancy in this project such that all customers of an org share the same database and this is isolated from other orgs. The Neon docs recommend project per user/org approach. I was wondering if just applying RLS would suffice. Any recommendations are helpful.
1 Reply
absent-sapphire•5mo ago
@Chavvi
https://neon.tech/use-cases/database-per-tenant really goes into detail of how using project per user/org would turn out to be the best approach as your application grows to have lot of tenants (that eventually run into noisy neighbout problem).