wolverine
wolverine copied to clipboard
Next Generation .NET Command and Message Bus
Every new version of .NET gives us a new bootstrapping mechanism. `UseWolverine()` today depends on `IHostBuilder` and won't help w/ `Host.CreateApplicationBuilder()`
* Would depend on making assumptions about other container behavior. Might use Lamar strictly to "plan" using the otherwise built in `ServiceCollection`
I have created a new test to simulate multi-tenancy support with two Wolverine nodes in balanced mode. The test is failing because agent assignments for new tenants are not properly...
**Is your feature request related to a problem? Please describe.** With the added support for dynamically adding tenants and spin up their agents (which is great 💯btw) we face an...
Audit members are now also added as structured logging context to the Microsoft ILogger in message handler chain if any Audited members are present in the Chain AuditedMembers list or...
This comes up often enough it's time to do something about it. Let's say that there's a use case for the exact same message & message type to be handled...
Using WriteById should return 404 as described here: https://martendb.io/documents/aspnetcore.html#single-document That works with ASP.Net MinimalAPI but with WolverineGet it returns 204 instead. Example that returns 204: ``` [WolverineGet("/warehouse/{warehouseId}")] public static Task...
Starting with "Wolverine is *not* MediatR" so please don't automatically use it that way.