🐎 Chapar

Chapar is a clean, extensible, and business‑friendly messaging abstraction for .NET. It hides the complexity of RabbitMQ and MassTransit behind a minimal API, while providing out‑of‑the‑box support for the Outbox, Inbox, and Pipeline patterns.

Inspired by the ancient Persian courier system – fast, reliable, and invisible to the message sender.

Why Chapar?

• Zero ceremony: PublishAsync and SendAsync are all you need.
• Transparent Outbox / Inbox: Add one NuGet package and every message is automatically stored in the database before delivery. No code changes.
• Pipeline: a chain of configurable behaviours (logging, error handling, validation, …) that wrap every handler.
• Framework agnostic: works standalone or on top of Zamin.
• Transport agnostic: currently uses MassTransit v8 (free & community‑supported), with Wolverine coming soon.

Packages

Package	Description
Chapar (Chapar.Core)	Core abstractions: IChaparBus, IMessageHandler<T>, Outbox/Inbox contracts
Chapar.MassTransit	MassTransit + RabbitMQ implementation
Chapar.MassTransit.Outbox	MassTransit + EF Outbox + RabbitMQ integration
Chapar.Pipeline	Extensible message handling pipeline
Chapar.Outbox.EntityFrameworkCore	EF Core‑based Outbox (transparent decorator)
Chapar.Inbox.EntityFrameworkCore	EF Core‑based Inbox (idempotency filter)
Chapar.Zamin	Bridges Chapar with the Zamin framework
Chapar.Zamin.MassTransit	One‑line setup for Chapar + Zamin + MassTransit
Chapar.Zamin.Outbox	Outbox/Inbox stores backed by Zamin's native tables

Quick start (standalone)

dotnet add package Chapar
dotnet add package Chapar.MassTransit

services.AddChaparMassTransit(opt => opt.Host = "localhost");

// Define a message
public record OrderPlaced(Guid OrderId) : IEvent;

// Publish
var bus = provider.GetRequiredService<IChaparBus>();
await bus.PublishAsync(new OrderPlaced(Guid.NewGuid()));

// Handle
public class OrderPlacedHandler : IMessageHandler<OrderPlaced>
{
    public Task HandleAsync(OrderPlaced message, CancellationToken ct)
    {
        Console.WriteLine($"Order {message.OrderId} received.");
        return Task.CompletedTask;
    }
}

Documentation

• Complete Guide – from simple publish/subscribe to advanced Outbox/Inbox, Pipeline, and Zamin integration.
• API Reference

Roadmap / Backlog

We welcome contributions! If you are interested in any of the items below, feel free to open an issue or send a pull request.

✅ Completed

Feature / Package	Description
Chapar.Core	Core abstractions and contracts
Chapar.MassTransit	MassTransit v8 integration
Chapar.MassTransit.Outbox	MassTransit v8 EF Outbox integration
Chapar.Pipeline	Pipeline behaviour infrastructure (diagnostics, error handling, etc.)
Chapar.Outbox.EntityFrameworkCore	Outbox store backed by EF Core
Chapar.Inbox.EntityFrameworkCore	Inbox store backed by EF Core
Chapar.Zamin	Zamin framework integration (replaces ISendMessageBus)
Chapar.Zamin.MassTransit	One‑line setup for Chapar + Zamin + MassTransit
Chapar.Zamin.Outbox	Outbox/Inbox stores backed by Zamin's native tables

🚧 In Progress (by core team)

Feature / Package	Description
Chapar.RoutingSlip	Content‑based routing (Courier / Routing Slip)
Chapar.Saga	Saga / Process Manager (state machine) support

💡 Backlog (up for grabs – contributions welcome!)

Feature / Package	Description
Chapar.Wolverine	Wolverine transport adapter
Chapar.Outbox.Dapper	Outbox store using Dapper
Chapar.Inbox.Dapper	Inbox store using Dapper
Chapar.Outbox.InMemory	In‑memory Outbox (for testing / lightweight scenarios)
Chapar.Inbox.InMemory	In‑memory Inbox (for testing)
Chapar.Outbox.Redis	Outbox store backed by Redis
Chapar.Inbox.Redis	Inbox store backed by Redis
Chapar.RequestResponse	Stronger abstractions for request/response patterns
Chapar.FluentValidation	Pre‑built pipeline behaviour for FluentValidation
Chapar.Authorization	Security behaviour for header/token checks
Chapar.Outbox.MongoDB	Outbox store for MongoDB
Chapar.Inbox.MongoDB	Inbox store for MongoDB
Management / Observability	Dashboard, dead‑letter browser, metrics

License

MIT