Skip to content
18th October 2026Serverless Wolverine, Outbox IncludedWolverine 6.51 adds DurabilityMode.ServerlessWithOutbox so you can write Wolverine handlers in Cloud Run, Lambda, or Azure Functions and still keep the transactional outbox, without any of the always-on background processes a normal Wolverine node depends on. Here's the problem that drove it, how the new mode works, the externally triggered durability pass that recovers anything that didn't get sent, how to receive messages by push, and why Wolverine 6's break from runtime compilation finally makes it a reasonable choice for serverless at all.7th October 2026Wolverine's End to End Multi-TenancyWolverine treats the tenant id as message metadata, and that one decision carries the tenant from HTTP detection, into the right Marten, Polecat, or EF Core session, onto every cascaded message, and into the only transactional inbox and outbox in .NET that lives in each tenant's own database. Here's how the whole chain works, and why it took years to get right.22nd April 2026Like Vertical Slice Architecture? Meet Wolverine.HTTP!Wolverine.HTTP is a first-class HTTP framework for ASP.NET Core built for vertical slice architecture — low ceremony, no Mediator library, built-in transactional outbox, and middleware more powerful than IEndpointFilter.21st April 2026EF Core is Better with WolverineWolverine has a strong development and production-time story for EF Core developers — transactional middleware, automatic outbox/inbox, runtime database migrations, test data resets, and declarative persistence.
Transactional Outbox
Posts tagged Transactional Outbox
18th October 2026Serverless Wolverine, Outbox IncludedWolverine 6.51 adds DurabilityMode.ServerlessWithOutbox so you can write Wolverine handlers in Cloud Run, Lambda, or Azure Functions and still keep the transactional outbox, without any of the always-on background processes a normal Wolverine node depends on. Here's the problem that drove it, how the new mode works, the externally triggered durability pass that recovers anything that didn't get sent, how to receive messages by push, and why Wolverine 6's break from runtime compilation finally makes it a reasonable choice for serverless at all.7th October 2026Wolverine's End to End Multi-TenancyWolverine treats the tenant id as message metadata, and that one decision carries the tenant from HTTP detection, into the right Marten, Polecat, or EF Core session, onto every cascaded message, and into the only transactional inbox and outbox in .NET that lives in each tenant's own database. Here's how the whole chain works, and why it took years to get right.22nd April 2026Like Vertical Slice Architecture? Meet Wolverine.HTTP!Wolverine.HTTP is a first-class HTTP framework for ASP.NET Core built for vertical slice architecture — low ceremony, no Mediator library, built-in transactional outbox, and middleware more powerful than IEndpointFilter.21st April 2026EF Core is Better with WolverineWolverine has a strong development and production-time story for EF Core developers — transactional middleware, automatic outbox/inbox, runtime database migrations, test data resets, and declarative persistence.