Multi-Tenancy Support

[benschermel]

This feature request stems from the KeyDB Community feature request seen here: https://community.keydb.dev/t/multi-tenancy-support

The premise of this feature is that namespaces are created and bound to specific users. Unlike ACL’s, this feature will essentially maintain separate datasets under specific namespaces, handled automatically by KeyDB (would appear to user as its own database).

Data for all users would be contained in the same KeyDB instance/cluster, under the same RDB & database, however would be isolated via namespace.

Ex.

keydb-cli > AUTH userApassword
OK
keydb-cli > SET A value1
OK
keydb-cli > GET A 
“value1”
keydb-cli > AUTH userBpassword
OK
keydb-cli > GET A
(nil)
keydb-cli > SET A value2
OK
keydb-cli > GET A 
"value2"

[smolinari]

For my understanding, couldn't the ACL ability to filter access via a key "prefix" be close to something like a namespace?

This:

~objects:, will result in the client only be able to access keys matching the pattern objects:

So, for instance, instead of objects: as a prefix, I create a hash for each tenant as a prefix to their key and it is programatically added to the set and get commands (or any other where it would be necessary). Wouldn't that be building a type of namespace system too?

Or, would creating a namespace internally to KeyDB be doing anything differently? If yes, what would it be other than making a key prefix transparent?

Scott