asp.net core - Same 'ConnectionMultiplexer' for 'AddDataProtection' and 'AddStackExchang

admin管理员组

文章数量:1394057

I'm adding a Redis token cache with data protection and also persisting the data protection keys to Redis (Propably a different Redis cache located somewhere other than the same token cache server). I'm just not sure if I should create and reuse the same 'ConnectionMultiplexer' here

services.AddStackExchangeRedisCache(redisCacheOptions =>
{
redisCacheOptions.ConnectionMultiplexerFactory = redis;
}

as I'm using here

services.AddDataProtection()
        .SetApplicationName(appName)
        .PersistKeysToStackExchangeRedis(redis, $"{appName}_DataProtection-Keys");

Or just have the AddStackExchangeRedisCache take care of it by itself?

If yes, how would I do that and still being able to dispose of it? And should I add a different name and endpoints each time it is used?

I'm new at this, so I would appreciate some help :)

I'm adding a Redis token cache with data protection and also persisting the data protection keys to Redis (Propably a different Redis cache located somewhere other than the same token cache server). I'm just not sure if I should create and reuse the same 'ConnectionMultiplexer' here

services.AddStackExchangeRedisCache(redisCacheOptions =>
{
redisCacheOptions.ConnectionMultiplexerFactory = redis;
}

as I'm using here

services.AddDataProtection()
        .SetApplicationName(appName)
        .PersistKeysToStackExchangeRedis(redis, $"{appName}_DataProtection-Keys");

Or just have the AddStackExchangeRedisCache take care of it by itself?

If yes, how would I do that and still being able to dispose of it? And should I add a different name and endpoints each time it is used?

I'm new at this, so I would appreciate some help :)

• asp-core
• caching
• redis
• data-protection

Share Improve this question Follow edited Mar 17 at 6:42 Brando Zhang 28.7k66 gold badges4242 silver badges7070 bronze badges asked Mar 13 at 10:48 Super userSuper user 144 bronze badges

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

This is according to your actually requirement, normally, reuse the same ConnectionMultiplexer instance across different parts of your application is generally recommended to avoid the overhead of creating multiple connections.

The ConnectionMultiplexerFactory is design for reusing connections to caches.

Also the ConnectionMultiplexer is thread safe and for consideruing the dispose for it, I suggest you could consider register it as a singletion.

Like below:

IConnectionMultiplexer connectionMultiplexer =
    ConnectionMultiplexer.Connect(connectionString);

builder.Services.AddSingleton(connectionMultiplexer);

builder.Services.AddStackExchangeRedisCache(options =>
{
    options.ConnectionMultiplexerFactory =
        () => Task.FromResult(connectionMultiplexer);
});

本文标签：