LiteBus 6.0.0

LiteBus

<p align="center"> <img src="assets/logo/litebus-logo.svg" alt="LiteBus logo" width="360"> </p>

<p align="center"> <a href="https://github.com/litenova/LiteBus/actions/workflows/build-and-test.yml"><img src="https://github.com/litenova/LiteBus/actions/workflows/build-and-test.yml/badge.svg" alt="Build and test status"></a> <a href="https://codecov.io/gh/litenova/LiteBus"><img src="https://codecov.io/gh/litenova/LiteBus/graph/badge.svg?token=XBNYITSV5A" alt="Code coverage"></a> <a href="https://www.nuget.org/packages/LiteBus"><img src="https://img.shields.io/nuget/v/LiteBus.svg" alt="NuGet version"></a> <a href="https://www.nuget.org/packages/LiteBus"><img src="https://img.shields.io/nuget/dt/LiteBus.svg" alt="NuGet downloads"></a> <a href="https://github.com/litenova/LiteBus/releases"><img src="https://img.shields.io/github/v/release/litenova/LiteBus" alt="GitHub release"></a> <a href="https://github.com/litenova/LiteBus/blob/main/LICENSE"><img src="https://img.shields.io/github/license/litenova/LiteBus" alt="License"></a> <a href="https://dotnet.microsoft.com/download/dotnet/10.0"><img src="https://img.shields.io/badge/.NET-10.0-512BD4" alt=".NET 10"></a> <a href="https://litebus.io"><img src="https://img.shields.io/badge/docs-litebus.io-2f6fed" alt="Documentation"></a> </p>

LiteBus is a mediator and durable messaging library for .NET 10. Commands, queries, and events have separate contracts and pipelines. Inbox and outbox processing use explicit storage, dispatch, and ingress adapters, so an application references an external SDK only when it selects that integration.

Version 6.0.0 targets .NET 10 and introduces the current module, durable messaging, transport, and hosting model. Applications upgrading from v5 should follow the v5 to v6 migration guide, including its database replacement and data-migration guidance. See the v6 changelog for the complete release record.

Package Selection

Install the package for each application concern. The package brings its abstractions and lower-layer runtime dependencies with it.

The Dependency Graph lists every package, its architectural layer, and its direct references.

Read the published documentation at litebus.io, browse the package and feature index, or run the Fumadocs site locally from site.

Quick Start

Install one or more semantic mediator modules:

dotnet add package LiteBus.Commands.Extensions.Microsoft.DependencyInjection
dotnet add package LiteBus.Queries.Extensions.Microsoft.DependencyInjection
dotnet add package LiteBus.Events.Extensions.Microsoft.DependencyInjection

Define a command and one handler:

public sealed record CreateProductCommand(string Name, decimal Price) : ICommand<Guid>;

public sealed class CreateProductCommandHandler : ICommandHandler<CreateProductCommand, Guid>
{
    public Task<Guid> HandleAsync(
        CreateProductCommand command,
        CancellationToken cancellationToken)
    {
        var productId = Guid.NewGuid();
        return Task.FromResult(productId);
    }
}

Register the messaging and semantic features in one callback. The module registry validates the completed dependency graph, so callback order does not change build order:

builder.Services.AddLiteBus(liteBus =>
{
    var applicationAssembly = typeof(Program).Assembly;

    liteBus.AddMessaging(_ => { });
    liteBus.AddCommands(commands =>
        commands.RegisterFromAssembly(applicationAssembly));
    liteBus.AddQueries(queries =>
        queries.RegisterFromAssembly(applicationAssembly));
    liteBus.AddEvents(events =>
        events.RegisterFromAssembly(applicationAssembly));
});

Inject the mediator for the operation being performed:

var productId = await commandMediator.SendAsync(
    new CreateProductCommand("Widget", 9.99m),
    cancellationToken);

The Getting Started guide covers commands, queries, events, module declaration, and handler discovery.

Durable Messaging

An inbox stores a command before execution. An outbox stores an event before publication. Storage, dispatch, ingress, and hosted processing remain separate choices.

builder.Services.AddLiteBus(liteBus =>
{
    liteBus.AddMessaging(_ => { });
    liteBus.AddCommands(commands =>
        commands.RegisterFromAssembly(typeof(Program).Assembly));

    liteBus.AddInbox(inbox =>
    {
        inbox.Contracts.Register<CreateProductCommand>("catalog.create-product");
        inbox.UseInMemoryStorage();
        inbox.UseInProcessDispatch();
        inbox.EnableInboxProcessor();
    });
});

Use in-memory storage for tests and local behavior checks. Use the PostgreSQL or Entity Framework Core adapter when durable writes must participate in an application transaction. See Inbox, Outbox, and Transactional Messaging Writes.

Architecture

LiteBus projects follow an explicit dependency role matrix. Every shipping project is assigned one role, and architecture tests reject forbidden project edges and direct package references.

The project count is intentional. Inbox and outbox remain separate, each broker and store remains opt-in, and integration SDKs do not enter unrelated dependency graphs. See Architecture for the module lifecycle and package rules.

Documentation

Repository documentation is authoritative. Start with the Documentation Index.

Build and Test

dotnet restore LiteBus.slnx
dotnet build LiteBus.slnx --configuration Release --no-restore
dotnet test LiteBus.slnx --configuration Release --no-build
pwsh ./scripts/Test-Documentation.ps1

Docker is required for the PostgreSQL, AMQP, Kafka, AWS SQS emulator, Azure Service Bus emulator, and relational integration suites. The Integration Tests guide lists the CI categories and local commands.

Contributing

Read Contributing before changing public APIs, package references, module dependencies, or persisted envelope behavior.

LiteBus is licensed under the MIT License.