Top level databases hierarchy logic

[databrecht]

@radascuta

A little confusion came from the following: I make the first db at top level online, then create a key, then go work at my local shell and make the first db. Then I go back online, and my db is nested under the db first made online. Ok, that makes sense because it is under the authority of the parent key I logged into the system with through my local shell.

It’s indeed common confusion because we don’t provide a ‘root’ key.

@radascuta

However, on the Fauna dashboard at top level, the databases created at this level are not called databases.

This confuses me slightly, my databases are called databases so I’m not certain what you mean.

@radascuta

if a developer admin starts at the top level, then the top level key should be enough to access any child databases in this application/project?

With a top level admin key you can indeed gain access to child databases.

@radascuta

Also, is there documentation covering how to log in with multiple keys that relate respectively to multiple projects? I have not found this, but would appreciate a good direction.

There are documents on multi-tenancy but they might bias you towards using multiple databases for everything which is definitely not the best choice. The question always comes back to: “do you need transactions over the data stored in these multiple databases or not since we don’t provide that yet”. A lot of answers have been provided in other forum posts that might help you:

• Multi-tenant authentication strategies
• Best practice for SaaS multi-tenancy
• Does the multi-tenancy model support syncing schemas and aggregating across child databases?