4 ms·
Not really. Your queries don't have to contain tenant Id if as part of your tenant context they have a connection string to their tenant DB.
by yabai_yatsu 6y ago
Not really. Your queries don't have to contain tenant Id if as part of your tenant context they have a connection string to their tenant DB.
- jawr 6y agoWouldn’t that mean you’re holding lots of non reusable connections? I have recently been using row level security with a transaction middleware where I set the tenant ID. Nice article regarding it - https://aws.amazon.com/blogs/database/multi-tenant-data-isolation-with-postgresql-row-level-security/ https://aws.amazon.com/blogs/database/multi-tenant-data-isol...
- yabai_yatsu 6y agoWe have about 6 physical DB servers, each client has their own db/schema on one of those boxes. Several thousand clients each with 10s of users per client. It brings in $15m ARR. So, it works. We're wanting to move off that architecture to something more future proof, but it's not our biggest pain point at this point in time.