Kongroo.BuildingBlocks.Infrastructure 0.2.0

🦘 Kongroo.BuildingBlocks.Infrastructure

Infrastructure-layer building blocks for the infrastructure layer of my .NET microservices — an EF Core unit of work that dispatches domain events before saving, a schema-per-context base, a migration initializer, and the hosted runner that orders and runs startup initializers. Builds on Kongroo.BuildingBlocks.Application and EF Core.

Installation

dotnet add package Kongroo.BuildingBlocks.Infrastructure

Building blocks

Usage

public sealed class OrderingDbContext(DbContextOptions<OrderingDbContext> options)
    : RelationalDbContext<OrderingDbContext>(options), IRelationalDbContext
{
    public static string Schema => "ordering";

    public DbSet<Order> Orders => Set<Order>();

    protected override void OnModelCreating(ModelBuilder modelBuilder)
    {
        base.OnModelCreating(modelBuilder); // applies the "ordering" schema
        modelBuilder.Entity<Order>(order =>
        {
            order.HasKey(entity => entity.Id);
            order.Property(entity => entity.Id).HasConversion(id => id.Value, value => OrderId.From(value));
        });
    }
}

// Registration
services.AddApplication();
services.AddRelationalDbContext<OrderingDbContext>(options => options.UseNpgsql(connectionString));
services.AddDbInitializer<OrderingDbContext>();

// In a command handler
order.Place();              // buffers an OrderPlaced domain event
dbContext.Orders.Add(order);
await unitOfWork.CommitAsync(cancellationToken); // dispatch OrderPlaced, then persist

Design notes

• Dispatch before save: domain events are dispatched in UnitOfWork.CommitAsync before SaveChanges, so side effects share the one transaction and integration events that handlers publish through MassTransit's bus outbox are staged in the same SaveChanges. No SaveChangesInterceptor — it conflicts with MassTransit's EF outbox.
• MassTransit owns messaging: the integration-event outbox/inbox lives at the app level; this package ships nothing for it.
• Explicit strongly-typed-id conversions: configure them per-property in your IEntityTypeConfiguration<T> files.
• Opinionated AddRelationalDbContext: applies snake_case naming and, in Development, EF Core detailed errors and sensitive-data logging; your configureOptions runs last, so you can override.
• One namespace: the DI extensions live in the package namespace, so a single using Kongroo.BuildingBlocks.Infrastructure; brings the types and the AddX() helpers.

What's baked in

• Target: net10.0, nullable + implicit usings, warnings-as-errors, latest .NET analyzers + SonarAnalyzer.
• Dependencies: Kongroo.BuildingBlocks.Application (→ Domain), EF Core (Relational) with EFCore.NamingConventions, and the Microsoft.Extensions.*.Abstractions for hosting, logging, and DI.
• API stability: the public surface is tracked with the public-API analyzer.
• Packaging: deterministic build, SourceLink, symbols (snupkg), and a MinVer-derived version.

Requirements

• .NET 10 SDK or later.

License

MIT