Skip to main content

Inert connection-lifecycle contracts for Koan modules that share a Redis backend.

Total Downloads
2.4K
2,391
Published
Sep 9, 2026
1mo ago

Get Started

dotnet add package Sylin.Koan.Redis.Abstractions --version 1.0.12
ProductVersions
.NET
net10.0

README

Sylin.Koan.Redis.Abstractions

Supported, inert connection-lifecycle vocabulary for Koan modules that share a Redis backend.

Install

Application developers do not normally reference this package. Reference a functional Redis adapter such as Sylin.Koan.Data.Connector.Redis or Sylin.Koan.Cache.Adapter.Redis; it brings the backend implementation transitively and keeps AddKoan() as the only bootstrap call.

Module authors that only need the cross-module contract can reference it without activating Redis:

dotnet add package Sylin.Koan.Redis.Abstractions

Meaningful result

Module authors use IRedisConnectionProvider only when they need source-aware access to more than the default endpoint. Simple Redis consumers should inject StackExchange.Redis's standard IConnectionMultiplexer.

This lets a capability compile against Redis connection ownership while remaining inert until a functional Redis backend is present.

Guarantees and limits

  • The support claim covers the contract shape and its inertness; it does not make this package a Redis runtime.
  • This assembly contains no KoanModule, discovery adapter, or backend implementation.
  • Referencing it cannot activate Redis, open a connection, or add IConnectionMultiplexer to dependency injection.
  • IRedisConnectionProvider is a module integration contract, not an application bootstrap requirement.
  • Runtime consumers require the functional Sylin.Koan.Redis package, normally supplied transitively by a Redis adapter.

See TECHNICAL.md for the contract boundary.

Downloads by Version

Similar & Alternative Packages

Hand-picked matching NuGet libraries based on tags & ecosystem

Depended On By

Find packages that declare this package as a dependency. NuGet does not provide a reverse-dependency endpoint, so candidates are checked on demand.

Adoption Assessment

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

Compatibility metadata lists 1 target framework; confirm the exact target used by your application.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.