Skip to content

Add additional strategy to use transactions instead of scripts in StackExchange.Redis implementation #51874

Open
@cfgiugliano

Description

@cfgiugliano

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

The current implementation of StackExchange.Redis relies on LUA scripts.
From a first look it seems to be so in order to execute HSET/HMSET and EXPIRE as an atomic execution.

Althought in some environments EVAL command might be disabled for the users, making the current implementation unusable.

Describe the solution you'd like

Using transactions could maybe be a good alternative to scripts, in that case the RedisCacheOptions could expose a way to choose the strategy to use, either stick to the default implementation using scripts, or opt-in the use of transactions.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-middlewareIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewaresfeature-cachingIncludes: StackExchangeRedis and SqlServer distributed caches

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions