ITMakers.InfraestructureBase 1.3.5

ITMakers.Infraestructure.Base

ITMakers.Infraestructure.Base is a shared infrastructure library used across IT Makers solutions to centralize common .NET runtime concerns. It targets net9.0 and packages reusable building blocks for startup configuration, persistence conventions, transport adapters, observability, middleware, and shared support types.

This repository contains one solution and one class library project:

• solution: ITMakers.Infraestructure.Base.sln
• package project: ITMakers.Infraestructure.Base.csproj

Package

Published package:

• NuGet: ITMakers.InfraestructureBase

Install from the .NET CLI:

dotnet add package ITMakers.InfraestructureBase

What the Library Provides

The package currently groups several infrastructure capabilities that consuming services can use selectively:

• dependency injection and startup extensions
• EF Core base entities and entity configurations
• HTTP adapters for internal platform services
• Redis caching helpers
• RabbitMQ event bus support
• OpenTelemetry and health-check extensions
• ASP.NET Core exception middleware
• shared DTOs, constants, helpers, localization resources, and result wrappers

This is a shared infrastructure toolkit, not a full application framework. Some capabilities are generic, while others encode assumptions specific to current IT Makers ecosystems such as Rueda.

Main Integration Surface

The most relevant public entrypoints for consuming services are:

• AddInfraestructureServices
• UseRedisCache
• AddRuedaInfrastructureHealthChecks<TDbContext>
• AddRuedaOpenTelemetry
• UseExceptionHandler
• UseGuidAsDefaultKey

The package also exposes reusable contracts and shared abstractions such as:

• user/context services: IUserService, ICurrentUserRuedaService
• external adapters: IUserIdentityService, ILibraryFileService, IOpenAiService
• infrastructure services: ICacheService, IEventBus
• persistence primitives: BaseEntity, BaseEntityCore, BaseEntityConfiguration<TBase>, BaseEntityCoreConfiguration<TBase>

Quick Integration Notes

At a high level, consuming services typically use this package from startup and DI registration code.

services.AddInfraestructureServices();
services.UseRedisCache(configuration);
services.AddRuedaInfrastructureHealthChecks<MyDbContext>(configuration);
services.AddRuedaOpenTelemetry(configuration);

app.UseExceptionHandler();

Important integration notes:

• AddInfraestructureServices() does not register every public service exposed by the package.
• Some services may still require manual registration in the host application.
• HTTP-based adapters expect named HttpClient registrations such as "Identity" and "Library".
• OData consumers can use UseGuidAsDefaultKey() when they want Guid to act as the default key convention.

Minimal usage in a project

A host application will usually install the NuGet package and then register the needed services from Program.cs.

using ITMakers.Infraestructure.Base;
using ITMakers.Infraestructure.Base.Extensions;

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddHttpContextAccessor();
builder.Services.AddInfraestructureServices();
builder.Services.AddRuedaOpenTelemetry(builder.Configuration);
builder.Services.AddRuedaInfrastructureHealthChecks<MyDbContext>(builder.Configuration);

var app = builder.Build();

app.UseExceptionHandler();

app.Run();

Depending on the features you use, you may also need:

• named HttpClient registrations such as "Identity" and "Library"
• Redis configuration and UseRedisCache(configuration)
• MediatR and handler registrations for IEventBus usage
• PostgreSQL-compatible EF Core configuration if you rely on the shared base entity configurations

Consumer Prerequisites

Host applications are expected to provide part of the runtime environment used by this library.

Required platform pieces

• IHttpContextAccessor for user/context-driven services
• named HttpClient registrations for downstream services where applicable
• MediatR and handler registrations if the RabbitMQ event bus is used
• ASP.NET Core hosting abstractions for environment-aware services

Configuration expectations

The package currently depends on configuration conventions for areas such as:

• timezone handling
• OpenTelemetry exporters and service metadata
• Redis connectivity
• RabbitMQ health-check connectivity
• Keycloak health-check URLs

Configuration is not fully normalized across all helpers, so consumers should align with the specific extension or service they are using.

Persistence assumptions

The shared EF Core base configurations assume PostgreSQL conventions, including:

• uuid_generate_v4()
• uuid and timestamptz
• soft delete through the Condition column
• optimistic concurrency via PostgreSQL xmin in BaseEntityCoreConfiguration

Development and Validation

Preferred local validation:

dotnet build ITMakers.Infraestructure.Base.sln

Current repository facts:

• there is one solution and one class library project
• no local test project is currently present
• restore/build depends on NuGet access

In restricted environments, restore/build may fail if https://api.nuget.org/v3/index.json is not reachable.

Documentation

For deeper technical detail, use:

• : architecture reference, subsystem behavior, and compatibility-sensitive assumptions
• : repo-specific workflow, validation guidance, and agent guardrails

Use this README.md as the repository entrypoint, ARCHITECTURE.md for technical depth, and AGENTS.md for execution policy.