Truss 

Domain-Driven Design building blocks: entities, aggregate roots, value objects, typed identifiers, business rules and domain events. No external dependencies.

Contracts for the Truss application layer: commands, queries, handlers, pipeline behaviors, domain event dispatching and unit of work.

Integration event runtime for Truss: versioned JSON serialization, transactional outbox with retry and dead-letter, transport abstraction, in-memory transport and consumer dispatch with a unit of work per... More information

Application kernel for Truss: request and handler abstractions, dispatcher, validation and unit of work behaviors, and the auth, tenancy and authorization contracts the application layer programs against.

Contracts for Truss integration events: events, handlers, publisher and event naming with versioning.

Background job runtime for Truss: transactional enqueueing through the outbox, workers with retry and timeout, live progress, scheduled and recurring jobs.

Contracts for Truss background jobs: job definitions, scheduling, progress reporting and monitoring.

Observability for Truss: structured logging of every request, traces and metrics through the BCL ActivitySource and Meter, and ambient correlation ids. Everything opt-in.

Compile-time registration and dispatch for Truss: handlers and validators discovered at build time, missing handlers reported as build diagnostics, no startup reflection.

The Truss command line: scaffold projects, add modules over time through the manifest, and generate bounded contexts, commands and queries.

JWT authentication for Truss: PBKDF2 password hashing, access and refresh token issuing, and JwtBearer wiring. The user model stays in your domain.

Redis transport for Truss messaging: durable delivery over Redis Streams with consumer groups, pending message reclaim and dead-lettering.

ASP.NET Core integration for Truss: endpoint mapping for commands and queries with automatic ProblemDetails error responses, remote context endpoints, job and outbox management endpoints, correlation and... More information

Postgres transport for Truss messaging: durable table-backed queue with SKIP LOCKED competing consumers and LISTEN/NOTIFY as a low-latency wake-up signal.

OpenTelemetry bridge for Truss: exports the framework's traces, metrics and logs over OTLP with one registration, ready for any OTLP dashboard.

RabbitMQ transport for Truss messaging: durable delivery over quorum queues with publisher confirms, broker-side retry accounting and dead-lettering.

Entity Framework Core persistence for Truss: unit of work with automatic commit and domain event dispatching before save.

Contracts for Truss authentication: password hashing and token issuing, referenced by the application layer.

EF Core outbox for Truss messaging: integration events stored in the same transaction as the command and published after the commit.

EF Core job store for Truss: job records persisted in the application database, scheduled atomically with the command that enqueued them.