IBeam.Repositories 2.9.0

IBeam.Repositories

IBeam.Repositories contains the core repository contracts and base implementations used by IBeam services.

dotnet add package IBeam.Repositories

When To Use This

• You are building an IBeam service and need a clean persistence boundary.
• You want CRUD, archive, soft-delete, and tenant-aware conventions.
• You want services to depend on repository abstractions instead of a specific database provider.
• You are implementing a new repository provider for Azure Tables, SQL, OrmLite, EF, or another store.

What This Package Contains

Architecture Fit

API <-- DTO/model object --> Service <-- Entity --> Repository

Repositories only manage one entity type. They should not call other repositories, enforce business permissions, write audit logs directly, or hydrate DTOs with external lookup data. That work belongs in the service layer.

Code Example

public sealed class Product : IEntity, ITenantEntity, IArchivableEntity, IDeletableEntity
{
    public Guid Id { get; set; }
    public Guid TenantId { get; set; }
    public string Name { get; set; } = string.Empty;
    public bool IsArchived { get; set; }
    public bool IsDeleted { get; set; }
}

public sealed class ProductService
{
    private readonly IBaseRepositoryAsync<Product> _products;

    public ProductService(IBaseRepositoryAsync<Product> products)
    {
        _products = products;
    }

    public Task<Product?> GetAsync(Guid productId, CancellationToken ct)
        => _products.GetByIdAsync(productId, ct: ct);
}

Repository Options

Data Storage

This package does not create tables, containers, or database schema. Physical storage comes from provider packages.

Service Operations, Auditing, And Permissions

Repositories are below the service boundary. Permission checks and audit logging should wrap service calls, not raw repository calls. This keeps the service layer as the all-knowing gatekeeper for rules, logging, errors, and orchestration.

Extended Docs And Agent Guidance

• AI prompt: .agent/prompt.md
• Root implementation guide: ../.agent/implementation-guide.md
• Service logging and audit: ../docs/service-logging-and-audit.md
• Service operation permissions: ../docs/service-operation-permissions.md

Agents should keep repository code entity-focused and avoid circular service/repository dependencies.

Version Notes

• Targets net10.0.
• Package version is assigned by the repository release workflow.