Aicrosoft.DataAccess.Abstractions 8.0.0-beta.260130.2

Aicrosoft.DataAccess.Abstractions

Aicrosoft.DataAccess.Abstractions is the foundational library for the data access layer in the Aicrosoft framework. It defines the core interfaces and models used across various data providers (such as Entity Framework Core, Azure Table Storage, etc.), ensuring a consistent architectural pattern and decoupling business logic from concrete data technologies.

Design Goals

1. Technological Decoupling: Provide high-level abstractions for repositories and units of work, allowing business logic to remain independent of specific database implementations.
2. Architectural Consistency: Enforce the Repository and Unit of Work patterns across all data access components within the framework.
3. Fine-Grained Access Control: Separate read and write operations into distinct interfaces (IReadRepository and IWriteRepository) to support optimized query patterns and clear intent.
4. Standardized Data Models: Define common structures for entities, paging, and ordering to ensure consistent API contracts.
5. Extensibility and Resilience: Provide interfaces for connection string resolution and standardized exception handling for data-related errors.

Key Abstractions

• IRepository<TEntity, TKey>: The primary generic interface for data access, combining read, write, and common operations.
• IReadRepository<TEntity, TKey>: Optimized for read-only operations, supporting IQueryable (typically with tracking disabled) and raw SQL execution.
• IUnitOfWork: Manages transactions and atomic commits across multiple repository operations.
• IEntity<TKey> & Entity<TKey>: Standardized base for domain entities, including primary key support.
• PagedRecord<T>: A unified response model for paginated data, including metadata like current page, page size, and total count.
• IPagingRepository: Specifically designed for paginated queries with complex ordering requirements.
• IConnectionStringResolver: Allows for dynamic and environment-aware connection string management.

Usage

Since this is an abstractions library, it is primarily used as a dependency in business projects (to reference interfaces) and data projects (to implement them).

1. Defining a Domain Entity

using Aicrosoft.DataAccess.Data;

public class Book : Entity<int>
{
    public string Title { get; set; }
    public string Author { get; set; }
}

2. Using Repositories in Business Services

By relying on IRepository instead of a concrete DbContext, your services remain testable and database-agnostic.

using Aicrosoft.DataAccess.Repositories;

public class BookService
{
    private readonly IRepository<Book, int> _repository;

    public BookService(IRepository<Book, int> repository)
    {
        _repository = repository;
    }

    public async Task<Book?> GetBook(int id)
    {
        // IReadRepository provides access to Queryable or Get
        return await _repository.GetFastQueryable()
                                .FirstOrDefaultAsync(x => x.Id == id);
    }
}

3. Handling Paginated Results

using Aicrosoft.DataAccess.Data;

public async Task<PagedRecord<Book>> GetBooksPage(int pageIndex, int pageSize)
{
    // The framework provides extension methods to project IQueryable to PagedRecord
    return await _repository.GetFastQueryable()
                            .ToPageAsync(pageIndex, pageSize);
}

Related Projects

• Aicrosoft.DataAccess.EntityFrameworkCore: Concrete implementation of these abstractions for EF Core.
• Aicrosoft.DataAccess.AzureTable: Concrete implementation for Azure Table Storage.
• Aicrosoft.Extensions.Hosting: Used for host-based dependency injection integration.