How to use 2 different redis servers as IRedisClient as keyed services in DI

[arteny]

Can't find any easy way to do it.
Is it possible to add support it?
And may be it also relates #177 need be fixed first.

[imperugo]

Hi @arteny, thanks for opening this.

The library already supports multiple Redis server instances — you can register multiple RedisConfiguration objects (each with a unique Name, one marked IsDefault = true) and then resolve them at runtime through IRedisClientFactory:

// Registration (Startup / Program.cs)
services.AddStackExchangeRedisExtensions<SystemTextJsonSerializer>(new[]
{
    new RedisConfiguration
    {
        Name = "cache",
        IsDefault = true,
        Hosts = new[] { new RedisHost { Host = "redis-cache.example.com", Port = 6379 } }
    },
    new RedisConfiguration
    {
        Name = "session",
        Hosts = new[] { new RedisHost { Host = "redis-session.example.com", Port = 6379 } }
    }
});

// Usage — inject IRedisClientFactory
public class MyService(IRedisClientFactory factory)
{
    private readonly IRedisDatabase _cache = factory.GetRedisDatabase("cache");
    private readonly IRedisDatabase _session = factory.GetRedisDatabase("session");
}

Each configuration gets its own isolated connection pool, so there is no cross-contamination between instances — the old static bag issue from #177 was resolved a while ago.

That said, you're right that this isn't as ergonomic as .NET 8+ keyed services would be (i.e. [FromKeyedServices("cache")] IRedisClient). That's a valid feature request and the infrastructure is already in place internally — it's just the DI registration layer that needs the bridge. I'll track that as a future enhancement.

For now, IRedisClientFactory is the supported way to reach named instances.