Child Databases per User (Customer)

[ptpaterson]

You can also set aside the use of child databases and use separate collections or a single collection and separate data with ABAC roles.

Regarding separation into child databases:

@databrecht

The data separation is indeed very clean but there are also limitations to this approach

This question has come up a few other times here.

Multi-tenant authentication strategies

Hi everyone, I am looking for advice to see if my architectural decisions could be improved. I have an application with several customers. I want to give each customer an isolated child-database, due the benefits of true data isolation, better performance and less complex queries that child-databases provides vs having all the customers in the same DB. Here’s a simplified version of my planned architecture: MainDatabase users_collection user-1 user-2 user-3 … child-databases db-custom…

Does the multi-tenancy model support syncing schemas and aggregating across child databases?

I’ll try to answer to the best of my abilities and ask internally for a better response than mine , there is also this topic with a few answers that might interest you: Best practice for SaaS multi-tenancy Yes. However, you won’t be able to perform a query in one transaction over multiple child database which is probably a limitation you want to keep in mind if you set it up like that since it might not be convenient when you need to join customers with customer data. It’s feasib…

Best practice for SaaS multi-tenancy

thanks, @databrecht. I think creating database per client is not the right way for me. Maybe for B2E SaaS this could make sense as enterprise clients have other requirements. Calling this “multi tenancy” in Fauna docs was somewhat misleading (for me at least). I originally thought that each child database inherits the parent db schema, so I can define everything once, and get a guaranteed sandbox for each customer. Having this would be a real killer feature because it would guarantee that the…