Hi,
Just thought I’d add my voice to the argument as to why this shouldn’t be an enterprise feature… there’s one surprisingly mundane but very important capability that namespaces/schemas/tenants give us: and that is the ability to create an isolated environment for integration testing.
Without multi-tenancy, we are forced to spin up and configure individual dgraph instances for each testing scenario. This is really time consuming, parallelism is limited, and there is a physical limit to test throughput due to available resources.
A multi-tenancy feature would allow a single dgraph instance to simultaneously serve multiple testing scenarios isolated by namespaces. You could just keep a development dgraph server in cluster and run all your tests against efficiently.
Data integrity is already a bit of a challenge in graph databases, and many aspects fall on testing to get guarantees for. This would be a big help in developing confidence with our dgraph implementation.
Personally, I don’t really need any of the ACLs and associated fuss around multi-tenancy - those truly are enterprise features… But a way to create isolated environments in a single dgraph server would help uptake for integrity conscious developers!