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 there’s real separation between customers’ data, while I can still access everything from the parent DB if I ever need cross tenant data.
In other words, it’s like the “user key” solution, only built-in by the DB.