IdempotencyGuard.Redis 1.3.0

IdempotencyGuard.Redis

Redis-backed idempotency store for the IdempotencyGuard library. Uses atomic Lua scripts for claim coordination and native Redis key TTL for automatic expiry.

Installation

dotnet add package IdempotencyGuard.AspNetCore
dotnet add package IdempotencyGuard.Redis

Setup

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddIdempotencyGuard(options =>
{
    options.MissingKeyPolicy = MissingKeyPolicy.Reject;
});

builder.Services.AddIdempotencyGuardRedisStore("localhost:6379");

var app = builder.Build();
app.UseIdempotencyGuard();

How it works

All claim operations use atomic Lua scripts evaluated on the Redis server:

• Claim — SET NX with TTL to atomically acquire a key
• Complete — Stores the response and updates the entry state in a single script
• Release — Removes the key to allow retries after failure

Expired entries are cleaned up automatically by Redis key TTL — no background cleanup service needed.

Connection options

// The Redis package owns the connection lifecycle internally.
// AbortOnConnectFail is forced to false for resilient startup/reconnect behavior.
builder.Services.AddIdempotencyGuardRedisStore("localhost:6379");

// Advanced options
builder.Services.AddIdempotencyGuardRedisStore(options =>
{
    options.ConnectionString = "localhost:6379,connectTimeout=5000,syncTimeout=1000";
    options.KeyPrefix = "myapp:idempotency:";
    options.MinimumReconnectInterval = TimeSpan.FromSeconds(60);
});

Connections are created lazily on first use. If Redis is temporarily unavailable, the package keeps ownership of the multiplexer and attempts reconnects on demand. Reconnect attempts are throttled by MinimumReconnectInterval, and AbortOnConnectFail = false is always applied even if the connection string says otherwise.

Why Redis

• Atomic operations — Lua scripts guarantee consistency under concurrent access
• Native TTL — No background cleanup needed; Redis handles expiry
• Distributed — Works across multiple application instances out of the box
• Low latency — Sub-millisecond claim/response operations

Documentation

See the full documentation on GitHub for middleware configuration, selective fingerprinting, and production deployment guides.

License

MIT