Question: Does Spring Data Redis Support Runtime Multi-Tenancy for Redis Key Prefixing?

[srosio]

Hi Spring Data Redis Team,

I’m working on a multi-tenant application using Redis, and I need to ensure that Redis keys are prefixed with the tenant context (e.g., tenantA:User:123) to isolate data per tenant. However, I’ve been struggling with managing key prefixing through custom solutions, and it’s proving to be error-prone and difficult to maintain across various Redis operations.

My Question:

• Does Spring Data Redis have built-in support for runtime multi-tenancy or a way to automatically apply tenant-aware key prefixing across all Redis operations (e.g., SADD, SMEMBERS, HSET, etc.) based on the current tenant context?
• If not, is there an existing recommended approach to achieve this that doesn’t require extensive manual configuration or custom serializers?

I believe this functionality would be very beneficial for multi-tenant applications, and I would appreciate any advice or resources on how to implement this more effectively.

Thank you for your time and assistance!

[christophstrobl]

Thank you for reaching out.
Spring Data Redis does not offer any built in solution for this kind of scenario and likely never will.

As you already mentioned there's a variety of potential solutions ranging from a custom RedisSerializer for keys to subclassing or creating proxies. I'm sorry there is not the one recommended solution as all of the mentioned have their own requirements/limitations.

However, it feels like this is a question that would be better suited for Stack Overflow. We prefer to use GitHub issues only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it).