Reimaginate.ProcessingLockService.Redis 4.0.0

Reimaginate.ProcessingLockService.Redis

Optional Redis provider for ProcessingLockService 4.0.0 (.NET 10). Install this package in Redis applications; it brings the core service, Reimaginate.RedisClient and StackExchange.Redis dependencies. In-memory and Cosmos applications do not need it.

Registration

using Reimaginate.ProcessingLockService;
using Reimaginate.ProcessingLockService.Redis;

services.AddProcessingLockService(options =>
    options.WithRedisRepository(redis => redis.ConnString = redisConnectionString));

The callback overload creates a Redis client owned and disposed by the repository. To reuse a client managed by the application:

services.AddProcessingLockService(options => options.WithRedisRepository(existingRedisClient));

The application retains ownership of a supplied IRedisClient. Disposing the lock service does not close or dispose that shared client.

Direct repository construction

ProcessingLockInRedisRepository lives in this assembly while retaining its namespace, Reimaginate.ProcessingLockService.Repositories, and both constructor signatures:

using Reimaginate.ProcessingLockService;
using Reimaginate.ProcessingLockService.Repositories;

var options = new ProcessingLockServiceOptions()
    .WithRepository(new ProcessingLockInRedisRepository(existingRedisClient));

The provider retains the existing Redis keys, JSON payloads, TTLs, Lua transactions, tenant isolation, ownership tokens and error codes. The extraction requires no stored data migration. It does not change Redis connection settings or dependency versions.

Upgrade and verification

The 3.x instance methods ProcessingLockServiceOptions.WithRedisRepository(...) are now extension methods in this package. Add its package reference and import Reimaginate.ProcessingLockService.Redis, then recompile. Applications using the moved repository type must also recompile because its assembly identity changed.

See the repository's 4.0 migration guide for package selection, examples and compatibility details.

The existing Redis provider contract, repository and contention-diagnostics tests now reference this package. Its registration factory exercises the callback extension. Run the suite with Docker available to execute Redis Testcontainer tests:

dotnet test test/Reimaginate.ProcessingLockService.UnitTests/Reimaginate.ProcessingLockService.UnitTests.csproj --filter FullyQualifiedName~Redis