Replies: 1 comment 2 replies
-
A recent discussion about this: |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Would you consider adding multi tenant support to dragonflydb?
Use case
We are currently running separate redis instances for each website/application we host on our kubernetes clusters (>100 sites). Most of these sites are have a fairly low volume of traffic. This is sub-optimal for several reasons:
We would love to have a setup where we have a single redis (compatible) "cluster" (HA setup) that could be used by all websites (tenants).
see https://community.keydb.dev/t/multi-tenancy-support/78 for more discussion on the feature
Implementation idea:
The idea is that each user gets mapped to a namespace. Each namespace has it's own set of virtual databases (0..max_db_per_ns).
The combination of namespace + dbnum will map to a physical database, but this will be transparant to the user/application.
Besides the databases also the scripts + pubsub channels (and any other global resource) need to be namespaced, so a user in namespace A cannot affect anything of any other namespace.
Background:
I have proposed and implemented multi tenant support for keydb: Snapchat/KeyDB#374, but as their development has significantly slowed down and my PR is not yet merged after ~2 years, I am exploring other options to get this to a mainline redis compatible implementation.
If there is interest in adding this to dragonflydb I want to work on this
Beta Was this translation helpful? Give feedback.
All reactions