Package Description
License
—
Deps
3
Install Size
—
Vulns
✓ 0
Published
Feb 19, 2026
Package Description
License
—
Deps
3
Install Size
—
Vulns
✓ 0
Published
Feb 19, 2026
Quick "how to" section is here Documentation can be found here: MicroPlumberd Documentation
dotnet add package MicroPlumberd # For your domain
dotnet add package MicroPlumberd.Services # For IoC integration and CommandBus
dotnet add package MicroPlumberd.SourceGenerators # Code generators for Aggregates, EventHandlers and more.// Vanilla
string connectionString = $"esdb://admin:changeit@localhost:2113?tls=false&tlsVerifyCert=false";
var settings = EventStoreClientSettings.Create(connectionString);
var plumber = Plumber.Create(settings);However, typicly you would add plumberd to your app:
services.AddPlumberd();Suppose you want to save some small "state" to your EventStoreDB. For example. current configuration of your Raspherry PI Camera. You can expect that state would be dependend only on previous state.
record class CameraConfiguration : IVersionAware: {
public int Shutter {get;set;}
public float Contrast {get;set;}
// ...
public Guid Id { get; set; } = Guid.NewGuid();
public long Version { get; set; } = -1;
}
// To save the state:
var state = new CameraConfiguration { /* ... */ };
plumber.AppendState(state); // because CameraConfiguration implements IVersionAware,
// optimistic concurrency check will be performed.
// To retrive latest state:
var id = state.Id; // We need to have Id from somewhere...
var actual = plumber.GetState<CameraConfiguration>(id);Event-sourced aggregates are the guardians of transaction. They encapsulate object(s) that we want to threat in isolation to the rest of the world because we want its data to be consistent.
Event-sourced aggregates are "rehydrated" from history (its stream) every time we need them. This means that theirs streams should be relatively short ~1K events max, to accomplish this usually you would you "close-the-books" pattern.
For performance reasons, sometimes you would want to have "snapshots". Snapshots are saved in related snapshot stream. When you want to retrive an aggregate:
[Aggregate(SnapshotEvery = 50)]
public partial class FooAggregate(Guid id) : AggregateBase<Guid,FooAggregate.FooState>(id)
{
public record FooState { public string Name { get; set; } };
private static FooState Given(FooState state, FooCreated ev) => state with { Name = ev.Name };
private static FooState Given(FooState state, FooRefined ev) => state with { Name =ev.Name };
public void Open(string msg) => AppendPendingChange(new FooCreated() { Name = msg });
public void Change(string msg) => AppendPendingChange(new FooRefined() { Name = msg });
}
// And events:
public record FooCreated { public string? Name { get; set; } }
public record FooRefined { public string? Name { get; set; } }Comments:
If you want to create a new aggregate and save it to EventStoreDB:
FooAggregate aggregate = FooAggregate.New(Guid.NewGuid());
aggregate.Open("Hello");
await plumber.SaveNew(aggregate);
If you want to load aggregate from EventStoreDB, change it and save back to EventStoreDB
var aggregate = await plumber.Get<FooAggregate>("YOUR_ID");
aggregate.Change("World");
await plumber.SaveChanges(aggregate);[EventHandler]
public partial class FooModel
{
private async Task Given(Metadata m, FooCreated ev)
{
// your code
}
private async Task Given(Metadata m, FooRefined ev)
{
// your code
}
}Comments:
var fooModel = new FooModel();
var sub= await plumber.SubscribeEventHandler(fooModel);
// or if you want to persist progress of your subscription
var sub2= await plumber.SubscribeEventHandlerPersistently(fooModel);With SubscribeModel you can subscribe from start, from certain moment or from the end of the stream. If you want to use DI and have your model as a scoped one, you can configure plumber at the startup and don't need to invoke SubscribeEventHandler manually. Here you have an example with EF Core.
// Program.cs
services
.AddPlumberd()
.AddEventHandler<FooModel>();
// FooModel.cs
[EventHandler]
public partial class FooModel : DbContext
{
private async Task Given(Metadata m, FooCreated ev)
{
// your code
}
private async Task Given(Metadata m, FooRefined ev)
{
// your code
}
// other stuff, DbSet... etc...
}[EventHandler]
public partial class FooProcessor(IPlumber plumber)
{
private async Task Given(Metadata m, FooRefined ev)
{
var agg = FooAggregate.New(Guid.NewGuid());
agg.Open(ev.Name + " new");
await plumber.SaveNew(agg);
}
}Implementing a processor is technically the same as implementing a read-model, but inside the Given method you would typically invoke a command or execute an aggregate. A process would subscribe persistently.
Let's analyse this example:
Please note that Sql schema create/drop auto-generation script will be covered in a different article. (For now we leave it for developers.)
Comments:
[OutputStream(FooModel.MODEL_NAME)]
[EventHandler]
public partial class FooModel : DbContext
{
internal const string MODEL_VER = "_v1";
internal const string MODEL_NAME = $"FooModel{MODEL_VER}";
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
modelBuilder
.Entity<FooEntity>()
.ToTable($"FooEntities{MODEL_VER}");
}
private async Task Given(Metadata m, FooCreated ev)
{
// your code
}
private async Task Given(Metadata m, FooRefined ev)
{
// your code
}
}With LiteDB you can easily achive the same without a hassle of schema recreation.
[OutputStream(DbReservationModel.MODEL_NAME)]
[EventHandler]
public partial class DbReservationModel(LiteDatabase db)
{
internal const string MODEL_VER = "_v2";
internal const string MODEL_NAME = $"Reservations{MODEL_VER}";
public ILiteCollection<Reservation> Reservations { get; } = db.Reservations();
private async Task Given(Metadata m, TicketReserved ev)
{
Reservations.Insert(new Reservation() { RoomName = ev.RoomName, MovieName = ev.MovieName });
}
}
public static class DbExtensions
{
public static ILiteCollection<Reservation> Reservations(this LiteDatabase db) => db.GetCollection<Reservation>(DbReservationModel.MODEL_NAME);
}
public record Reservation
{
public ObjectId ReservationId { get; set; }
public string RoomName { get; set; }
public string MovieName { get; set; }
}
/// Configure your app:
services.AddEventHandler<DbReservationModel>(true)
If you want to start as quickly as possible, you can start with EventStoreDB as command-message-bus.
services.AddPlumberd()
.AddCommandHandler<FooCommandHandler>()
// on the client side:
ICommandBus bus; // from DI
bus.SendAsync(Guid.NewGuid(), new CreateFoo() { Name = "Hello" });If you are running many replicas of your service, you need to switch command-execution to persistent mode:
services.AddPlumberd(configure: c => c.Conventions.ServicesConventions().AreHandlersExecutedPersistently = () => true)
.AddCommandHandler<FooCommandHandler>()
This means, that once your microservice subscribes to commands, it will execute all. So if your service is down, and commands are saved, once your service is up, they will be executed. To skip old commands, you can configure a filter.
services.AddPlumberd(configure: c => {
c.Conventions.ServicesConventions().AreHandlersExecutedPersistently = () => true;
c.Conventions.ServicesConventions().CommandHandlerSkipFilter = (m,ev) => DateTimeOffset.Now.Substract(m.Created()) > TimeSpan.FromSeconds(60);
})
.AddCommandHandler<FooCommandHandler>()MetadataFactory centralizes Metadata construction with proper JSON schema. Available via plumber.MetadataFactory or standalone with new MetadataFactory() (uses default conventions).
// From an event object — conventions compute sourceStreamId and enrich metadata
var metadata = plumber.MetadataFactory.Create(context, evt, recipientId);
// With explicit sourceStreamId — for tests and simple scenarios
var factory = new MetadataFactory();
var metadata = factory.Create($"Category-{id}", created: DateTimeOffset.Now, userId: "admin");
// Typed — conventions compute sourceStreamId from event type
var metadata = factory.Create<OrderCreated, Guid>(orderId, evt, created: DateTimeOffset.Now);The factory ensures Metadata.StreamId<T>(), Metadata.Created(), Metadata.UserId() and other accessors work correctly by building the proper JSON Data schema.
/// Given simple models, where master-model has foreign-key used to obtain value from dimentionLookupModel
var dimentionTable = new DimentionLookupModel();
var factTable = new MasterModel(dimentionTable);
await plumber.SubscribeSet()
.With(dimentionTable)
.With(factTable)
.SubscribeAsync("MasterStream", FromStream.Start);Given you have written your domain, you can generate step files that would populate Ghierkin API to your domain.
If you'd like to use direct dotnet-dotnet communication to execute command-handlers install MicroPlumberd.DirectConnect
dotnet add package MicroPlumberd.Services.Grpc.DirectConnectIf you prefer direct communication (like REST-API, but without the hassle for contract generation/etc.) you can use direct communication where client invokes command handle using grpc. Command is not stored in EventStore.
/// Let's configure server:
services.AddCommandHandler<FooCommandHandler>().AddServerDirectConnect();
/// Add mapping to direct-connect service
app.MapDirectConnect();Here is an example of a command handler code:
[CommandHandler]
public partial class FooCommandHandler(IPlumber plumber)
{
[ThrowsFaultException<BusinessFault>]
public async Task Handle(Guid id, CreateFoo cmd)
{
if (cmd.Name == "error")
throw new BusinessFaultException("Foo");
var agg = FooAggregate.New(id);
agg.Open(cmd.Name);
await plumber.SaveNew(agg);
}
[ThrowsFaultException<BusinessFault>]
public async Task<HandlerOperationStatus> Handle(Guid id, ChangeFoo cmd)
{
if (cmd.Name == "error")
throw new BusinessFaultException("Foo");
var agg = await plumber.Get<FooAggregate>(id);
agg.Change(cmd.Name);
await plumber.SaveChanges(agg);
return HandlerOperationStatus.Ok();
}
}And how on the client side:
service.AddClientDirectConnect().AddCommandInvokers();
// And invocation
var clientPool = sp.GetRequiredService<IRequestInvokerPool>();
var invoker = clientPool.Get("YOUR_GRPC_URL");
await invoker.Execute(Guid.NewId(), new CreateFoo(){});Given diagram:
# Add required packages:
dotnet add package MicroPlumberd.Services.ProcessManagersThe code of Order Process Manager looks like this:
// Let's configure stuff beforehand
services.AddPlumberd(eventStoreConfig)
.AddCommandHandler<OrderCommandHandler>() // handles PlaceOrder command.
.AddProcessManager<OrderProcessManager>();
// And process manager.
[ProcessManager]
public class OrderProcessManager(IPlumberd plumberd)
{
public async Task<ICommandRequest<MakeReservation>> StartWhen(Metadata m, OrderCreated e)
{
return CommandRequest.Create(Guid.NewId(), new MakeReservation());
}
public async Task<ICommandRequest<MakePayment>> When(Metadata m, SeatsReserved e)
{
return CommandRequest.Create(Guid.NewId(), new MakePayment());
}
public async Task When(Metadata m, PaymentAccepted e)
{
var order = await plumberd.Get<Order>(this.Id);
order.Confirm();
await plumberd.SaveChanges(order);
}
// Optional
private async Task Given(Metadata m, OrderCreated v){
// this will be used to rehydrate state of process-manager
// So that when(SeatsReserved) you can adjust the response.
}
// Optional 2
private async Task Given(Metadata m, CommandEnqueued<MakeReservation> e){
// same here.
}
}
Uniqueness support in EventSourcing is not out-of-the-box, especially in regards to EventStoreDB. You can use some "hacks" but at the end of the day, you want uniqueness to be enforced by some kind of database. EventStoreDB is not designed for that purpose.
However, you can leverage typical reservation patterns. At the moment the library supports only the first option:
At domain-layer, a domain-service usually would enforce uniqueness. This commonly requires a round-trip to a database. So just before actual event(s) are saved in a stream, a check against uniqueness constraints should be evaluated - thus reservation is made. When the event is appended to the stream, a confirmation is done automatically (on db).
At a app-layer, command-handler would typically reserve a name. And when aggregate, which is being executed by the handler, saves its events successfully, then the reservation is confirmed. If the handler fails, then the reservation is deleted. Seems simple? Under the hood, it is not that simple, because what if the process is terminated while the command-handler is executing? We need to make sure, that we can recover successfully from this situation.
Let's see the API proposal:
// Let's define unique-category name
record FooCategory;
public class FooCreated
// and apply it to one fo the columns.
[Unique<FooCategory>]
public string? Name { get; set; }
// other stuff
}For complex types, we need more flexibility.
// Let's define unique-category name, this will be mapped to columns in db
// If you'd opt for domain-layer enforcment, you need to change commands to events.
record BooCategory(string Name, string OtherName) : IUniqueFrom<BooCategory, BooCreated>, IUniqueFrom<BooCategory, BooRefined>
{
public static BooCategory From(BooCreated x) => new(x.InitialName, x.OtherName);
public static BooCategory From(BooRefined x) => new(x.NewName, x.OtherName);
}
[Unique<BooCategory>]
public record BooCreated(string InitialName, string OtherName);
[Unique<BooCategory>]
public record BooRefined(string NewName, string OtherName);All "How to's" are in MicroPlumber.Tests projects, so you can easily run it!
Example event:
[OutputStream("ReservationStream")]
public record TicketReserved {
public string? MovieName { get; set; }
public string? RoomName { get; set; }
}Code:
public async Task HowToAppendEventToHisDefaultStream(IPlumber plumber)
{
var ourLovelyEvent = new TicketReserved();
var suffixOfStreamWhereOurEventWillBeAppend = Guid.NewGuid();
await plumber.AppendEvent(ourLovelyEvent, suffixOfStreamWhereOurEventWillBeAppend);
}Code:
public async Task HowToAppendEventToSpecificStream(IPlumber plumber)
{
var streamIdentifier = Guid.NewGuid();
var ourLovelyEvent = new TicketReserved();
await plumber.AppendEventToStream($"VIPReservationStream-{streamIdentifier}", ourLovelyEvent);
}Model:
[OutputStream("ReservationModel_v1")]
[EventHandler]
public partial class ReservationModel(InMemoryModelStore assertionModelStore)
{
public InMemoryModelStore ModelStore => assertionModelStore;
public bool EventHandled{ get; set; } = false;
private async Task Given(Metadata m, TicketReserved ev)
{
EventHandled = true;
assertionModelStore.Given(m, ev);
await Task.Delay(0);
}
}Code:
public async Task HowToMakeAModelSubscribe(IPlumber plumber)
{
var fromWhenShouldWeSubscribeOurStream = FromRelativeStreamPosition.Start;
var modelThatWantToSubscribeToStream = new ReservationModel(new InMemoryModelStore());
await plumber.SubscribeEventHandler(modelThatWantToSubscribeToStream, start: fromWhenShouldWeSubscribeOurStream);
var suffixOfStreamWhereOurEventWillBeAppend = Guid.NewGuid();
var ourLovelyEvent = new TicketReserved();
await plumber.AppendEvent(ourLovelyEvent, suffixOfStreamWhereOurEventWillBeAppend);
await Task.Delay(1000);
modelThatWantToSubscribeToStream.EventHandled.Should().BeTrue();
}Code:
public async Task HowToMakeAModelSubscribeButFromLastEvent(IPlumber plumber)
{
var modelThatWantToSubscribeToStream = new ReservationModel(new InMemoryModelStore());
var suffixOfStreamWhereOurEventWillBeAppend = Guid.NewGuid();
var someVeryOldEvent = new TicketReserved();
await plumber.AppendEvent(someVeryOldEvent, suffixOfStreamWhereOurEventWillBeAppend);
await Task.Delay(1000);
await plumber.SubscribeEventHandler(modelThatWantToSubscribeToStream, start: FromRelativeStreamPosition.End-1);
modelThatWantToSubscribeToStream.EventHandled.Should().BeFalse();
var ourLovelyEvent = new TicketReserved();
await plumber.AppendEvent(ourLovelyEvent, suffixOfStreamWhereOurEventWillBeAppend);
await Task.Delay(1000);
modelThatWantToSubscribeToStream.EventHandled.Should().BeTrue();
}Projection:
[EventHandler]
public partial class TicketProjection(IPlumber plumber)
{
private async Task Given(Metadata m, TicketReserved ev)
{
await plumber.AppendLink($"RoomOccupancy-{ev.RoomName}", m);
}
}Model:
[EventHandler]
public partial class RoomOccupancy
{
public int HowManySeatsAreReserved { get; set; }
private async Task Given(Metadata m, TicketReserved ev)
{
HowManySeatsAreReserved++;
}
}Code:
public async Task HowToLinkEventsToAnotherStream(IPlumber plumber)
{
var ourLovelyEvent = new TicketReserved()
{
MovieName = "Scream",
RoomName = "Venus"
};
await plumber.SubscribeEventHandlerPersistently(new TicketProjection(plumber));
await plumber.AppendEvent(ourLovelyEvent);
await plumber.Subscribe($"RoomOccupancy-{ourLovelyEvent.RoomName}", FromRelativeStreamPosition.Start)
.WithHandler(new RoomOccupancy());
}Model:
[OutputStream("ReservationModel_v1")]
[EventHandler]
public partial class ReservationModel(InMemoryModelStore assertionModelStore)
{
public InMemoryModelStore ModelStore => assertionModelStore;
public bool EventHandled{ get; set; } = false;
private async Task Given(Metadata m, TicketReserved ev)
{
EventHandled = true;
assertionModelStore.Given(m, ev);
await Task.Delay(0);
}
}Code:
public async Task HowToRehydrateModel(IPlumber plumber)
{
var modelThatWantToSubscribeToStream = new ReservationModel(new InMemoryModelStore());
var suffixOfStreamWhereOurEventWillBeAppend = Guid.NewGuid();
var ourLovelyEvent = new TicketReserved();
await plumber.AppendEvent( ourLovelyEvent, suffixOfStreamWhereOurEventWillBeAppend);
await Task.Delay(1000);
await plumber.SubscribeEventHandler(modelThatWantToSubscribeToStream, start: FromRelativeStreamPosition.Start);
await Task.Delay(1000);
modelThatWantToSubscribeToStream.EventHandled.Should().BeTrue();
modelThatWantToSubscribeToStream.EventHandled = false;
modelThatWantToSubscribeToStream.EventHandled.Should().BeFalse();
await plumber.Rehydrate(modelThatWantToSubscribeToStream,
$"ReservationStream-{suffixOfStreamWhereOurEventWillBeAppend}");
modelThatWantToSubscribeToStream.EventHandled.Should().BeTrue();
}