Cirreum.Runtime.Persistence.SQLite 1.0.4

Cirreum.Runtime.Persistence.SQLite

Simplified Cirreum.Persistence.SQLite configuration for Cirreum runtime applications

Overview

Cirreum.Runtime.Persistence.SQLite provides a unified persistence layer configuration for the Cirreum framework. It simplifies database integration by offering a single extension method that automatically registers and configures multiple persistence providers with built-in health checks.

Installation

dotnet add package Cirreum.Runtime.Persistence.SQLite

Usage

Add persistence to your application with a single line:

var builder = WebApplication.CreateBuilder(args);

// Add persistence support
builder.AddPersistence();

var app = builder.Build();

This automatically:

• Registers SQLite persistence services
• Configures health checks for database connectivity
• Prevents duplicate service registration
• Integrates with the Cirreum service provider infrastructure

Supported Providers

Features

• Simple Integration: One method to configure all persistence needs
• Health Checks: Automatic health check registration for monitoring
• Duplicate Prevention: Smart registration prevents service conflicts
• Extensible Design: Built on the Cirreum service provider pattern for easy extension

Configuration

Configure persistence providers in appsettings.json:

{
  "ServiceProviders": {
	"Persistence": {
	  "SQLite": {
		"default": {
		  "Name": "MySQLite",
		  "CommandTimeout": 60,
		  "EnableHealthCheck": true
		}
	  }
	}
  },
  "ConnectionStrings": {
	"MySQLite": "Data Source=mydb.sqlite;" // prefer Azure Key Vault for production
  }
}

The Name property resolves the connection string via Configuration.GetConnectionString(name). For production, store connection strings in a Key Vault using the naming convention ConnectionStrings--{Name}.

For detailed configuration options, see the individual provider documentation:

• Cirreum.Persistence.Sql (abstractions)
• Cirreum.Persistence.SQLite (implementation)

Versioning

Cirreum.Runtime.Persistence follows Semantic Versioning:

• Major - Breaking API changes
• Minor - Truly new features, backward compatible
• Patch - Update nuget packages, Bug fixes, backward compatible

Given its foundational role, major version bumps are rare and carefully considered.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Cirreum Foundation Framework
Layered simplicity for modern .NET