I thought more about this and this might not be required. I think a good way to find out about the exact requirements might be to look at what all do we need for this to work with Slash GraphQL. A user having their own Dgraph instance deployed in Slash GraphQL would not access data in another namespace (belonging to another user). Guardians (superusers) are the only users that might be able to access data across namespaces.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Make Multi-Tenancy open source | 35 | 3105 | January 1, 2022 | |
| Building SaaS apps with Slash (and open source Dgraph) | 12 | 698 | March 22, 2021 | |
| Multi-Tenancy 2021 | 1 | 1528 | March 10, 2021 | |
| If google would use dgraph, should it use for everything one single dgraph DB, or for every service (Maps, YouTube, GMail...) an own dgraph DB? | 10 | 854 | October 21, 2021 | |
| Support Multi-Tenancy | 22 | 1608 | June 3, 2020 |