I’d like to know more about the use cases for Faunadb’s multi-tenancy.
When the Fauna documentation talks about multi-tenancy for clients is it referring to multiple client projects that are different, or segmenting customers within a single product (same schema in multiple children)?
For example, let’s say we have two verticals / bounded contexts / micro services. Having a user’s token restricted to their company’s child database would make the security model much easier (no more policies in code checking arguments vs foreign keys like a Pundit policy in Rails).
- Is Faunadb’s vision of client databases applicable to something this:
- If this is hundreds or thousands of child databases is that an issue?
- Is there a way to sync all of the child databases at once to maintain graphql schema updates?
- Can we aggregate across all these child databases for internal metrics and reporting?
I see the
Databases function, so I guess we could write fan out code, but is this above approach supported / recommended?
Thanks for any guidance on this from the Faunadb team,