ZeroCaching 1.0.2

ZeroCaching

ZeroCaching is a lightweight and configurable distributed caching library for .NET applications.
It provides a unified caching abstraction that allows applications to enable, disable, or switch cache providers through configuration without changing application code.

Project Structure

src
└── ZeroCaching
    ├── ZeroCaching.csproj
    ├── Abstractions
    ├── Configuration
    ├── Factories
    ├── Services
    ├── Validation
    ├── Internals
    └── DependencyInjection

Why ZeroCaching?

• Simple integration with existing .NET applications
• Configuration-driven setup
• Supports distributed caching
• Built-in fallback when caching is disabled
• Startup configuration validation
• Dependency Injection friendly

Installation

dotnet add package ZeroCaching

Configuration

ZeroCaching is configured using the appsettings.json file.
This allows you to enable or disable caching and switch providers without changing code.

appsettings.json

{
  "Cache": {
    "Enabled": true,
    "Provider": "Redis",
    "ConnectionString": "your-redis-connection-string",
    "DefaultExpirationMinutes": 30
  }
}

Configuration Options

Example Configuration Scenarios

Disable Caching

{
  "Cache": {
    "Enabled": false
  }
}

Redis Configuration

{
  "Cache": {
    "Enabled": true,
    "Provider": "Redis",
    "ConnectionString": "localhost:6379",
    "DefaultExpirationMinutes": 60
  }
}

Service Registration

builder.Services.AddZeroCaching(builder.Configuration);

Usage

Store Data

await cacheService.SetAsync("product:1", product);

Retrieve Data

var product = await cacheService.GetAsync<Product>("product:1");

Check Existence

var exists = await cacheService.ExistsAsync("product:1");

Remove Data

await cacheService.RemoveAsync("product:1");

How It Works

• Configure caching through appsettings.json
• Register ZeroCaching in application startup
• Inject cache service where needed
• Use caching without worrying about provider-specific logic

Supported Providers

Benefits

• Easy configuration
• Provider-agnostic usage
• Distributed caching support
• Environment-based configuration
• Clean .NET Dependency Injection integration