Multi tenant client to serve serverless usecases.

[srikar-jilugu]

We have a use case where we need to connect to multiple serverless Redis caches (e.g., AWS ElastiCache Serverless, Redis Labs etc) dynamically. However, current redis clients are designed to interact with a single cluster, requiring periodic topology updates, which makes them incompatible with multi-tenant scenarios.

With the introduction of serverless offerings, a stateless client that can dynamically route commands among multiple endpoints without any need to maintain cluster state could better serve the usecases Most existing clients assume a single cluster and require ongoing topology updates, which aren't required for serverless caches(ref)

Why Not Use Multiple Clients?

This is a feasible solution, but it requires us to maintain the set of hosts as to initialise the clients during startup and maintaining multiple clients is memory heavy

Feature Request

A lightweight, stateless redis client that:

• Can maintain independent connection pools for multiple endpoints and dynamically routes commands
• wouldn't require it to keep track of cluster topology and handle routing to replicas.

Is there any ongoing work or plans for something like this? Would love to discuss possible approaches!

[ndyakov]

Hello @srikar-jilugu, there is no ongoing work for such client implementation. The cluster client itself needs to know the topology to be able to route the requests appropriately base on the response of

go-redis/osscluster.go

Line 1862 in 162a154

func (c *ClusterClient) cmdNode(

for example. Redis Enterprise handles that routing and expose a single endpoint, then a basic single instance Client can work with the said endpoint.

[srikar-jilugu]

Redis Enterprise handles that routing and expose a single endpoint

By Redis Enterprise, do you mean the serverless offering by redis? If so, we are looking for a client that is not bound to a single serverless cache but can be used with multiple caches simultaneously, similar to how the aws dynamodb sdk operates for eg.

then a basic single instance Client can work with the said endpoint.

Yes, a client that internally does nothing but what a basic single-instance client would do, but for multiple caches.

[srikar-jilugu]

For eg, client can be used this way

ctx.Set(cacheName, "tenant1")
serverlessClient.Get(ctx, "key")

or

cacheName = "tenant1"
serverlessClient.Get(ctx, cacheName, "key")