Going through tutorials and easing into it, trying to understand best practices.
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.
However, on the Fauna dashboard at top level, the databases created at this level are not called databases. Are the top level databases more like projects or apps or schemas? Moreover, for development purposes, 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?
What I am trying to understand is the multiple tenancy vs different projects or apps at the top level. Are there documents that explain what the best approach is for a developer that may work on different projects or related projects with common functions?
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.
Thanks in advance.