Skip to content
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.
1st October 2026Fisher: A Document Database for Anywhere SQLite is a Good ChoiceFisher gets talked about as the Critter Stack's event store on SQLite, but it's also a full document database that lives in a file inside your own process. If SQLite is the right storage for your application, Fisher is a much lower ceremony way to use it than EF Core: no mapping, no migration files, schema changes that just work through Weasel, and a first class Wolverine integration.22nd September 2026Multi-Tenancy with EF Core is a Whole Lot Easier with WolverineEF Core query filters and dynamic connection strings are the raw ingredients for multi-tenancy. Wolverine turns them into a finished dish: conjoined tenancy with zero filter plumbing, database per tenant, tenants added at runtime, HTTP tenant detection that flows straight into DbContext construction, a transactional inbox/outbox per tenant database, tenant ids that ride along on every cascaded message, and 'it just works' schema migrations across every tenant database.
30th August 2026Clone, docker compose up, Go: Friction-Free EF Core Integration Testing with Weasel and WolverineWeasel manages the schema for every EF Core DbContext in your application the same way it has always managed Marten's -- and its FK-aware database cleaner plus IInitialData give you a fast, repeatable reset between tests. Clean clone to green test suite with no migration chain to run.29th August 2026Generate EF Core Migrations From Your Real Database Schema with WeaselWeasel can now generate EF Core migrations from a Weasel schema model or an existing database -- bridging Critter Stack schema management into the standard EF Core migrations workflow.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.
EF Core
Posts tagged EF Core
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.1st October 2026Fisher: A Document Database for Anywhere SQLite is a Good ChoiceFisher gets talked about as the Critter Stack's event store on SQLite, but it's also a full document database that lives in a file inside your own process. If SQLite is the right storage for your application, Fisher is a much lower ceremony way to use it than EF Core: no mapping, no migration files, schema changes that just work through Weasel, and a first class Wolverine integration.22nd September 2026Multi-Tenancy with EF Core is a Whole Lot Easier with WolverineEF Core query filters and dynamic connection strings are the raw ingredients for multi-tenancy. Wolverine turns them into a finished dish: conjoined tenancy with zero filter plumbing, database per tenant, tenants added at runtime, HTTP tenant detection that flows straight into DbContext construction, a transactional inbox/outbox per tenant database, tenant ids that ride along on every cascaded message, and 'it just works' schema migrations across every tenant database.30th August 2026Clone, docker compose up, Go: Friction-Free EF Core Integration Testing with Weasel and WolverineWeasel manages the schema for every EF Core DbContext in your application the same way it has always managed Marten's -- and its FK-aware database cleaner plus IInitialData give you a fast, repeatable reset between tests. Clean clone to green test suite with no migration chain to run.29th August 2026Generate EF Core Migrations From Your Real Database Schema with WeaselWeasel can now generate EF Core migrations from a Weasel schema model or an existing database -- bridging Critter Stack schema management into the standard EF Core migrations workflow.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.