Stratara.Mediator
4.7.0
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Mediator --version 4.7.0
NuGet\Install-Package Stratara.Mediator -Version 4.7.0
<PackageReference Include="Stratara.Mediator" Version="4.7.0" />
<PackageVersion Include="Stratara.Mediator" Version="4.7.0" />
<PackageReference Include="Stratara.Mediator" />
paket add Stratara.Mediator --version 4.7.0
#r "nuget: Stratara.Mediator, 4.7.0"
#:package Stratara.Mediator@4.7.0
#addin nuget:?package=Stratara.Mediator&version=4.7.0
#tool nuget:?package=Stratara.Mediator&version=4.7.0
Stratara.Mediator
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
License: MIT.
In-process mediator with DI-resolved handlers and pipeline behaviors. Drop-in replacement for MediatR-style routing without the runtime cost of MethodInfo.Invoke — uses a typed wrapper cache and direct DI dispatch.
Quick start
services.AddMediator()
.AddCommandHandlersFromAssemblyContaining<Program>()
.AddQueryHandlersFromAssemblyContaining<Program>()
.AddPipelineBehaviorWithResult(typeof(LoggingBehavior<,>))
.AddPipelineBehavior(typeof(LoggingBehavior<>));
// Optional: wrap in authorization decorator
services.AddAuthorizingMediator<MyAuthorizationProvider>();
Every dispatch is traced as a span named Handle <RequestType>. The spans come from the
Stratara.Application activity source — subscribe to it and they appear; register your own
OpenTelemetry Tracer and the mediator uses that instead. Nothing has to be registered for the
mediator to start.
IMediator is registered scoped. Resolve it from a scope (a request scope in ASP.NET Core, or
an explicit IServiceProvider.CreateScope() in a console host) — resolving it from the root
provider throws.
What's in the box
IMediator.HandleAsync<TResult>(IRequest<TResult>, CancellationToken)— routes queries and commands-with-result toIQueryHandler<TRequest, TResult>through any registeredIPipelineBehavior<TRequest, TResult>chain.IMediator.HandleAsync<TRequest>(TRequest, CancellationToken)— routes void commands toICommandHandler<TRequest>through any registeredIPipelineBehavior<TRequest>chain.AuthorizingMediatordecorator — checks[RequireRole]attributes viaIAuthorizationProviderand[RequirePermission]attributes viaIPermissionResolver(both AND) on the request's runtime type before delegating to the inner mediator. Its startup validator fails fast when a permission-guarded type is registered without an authorizing mediator or without a resolver, so a guard can never be silently skipped.BucketLockPool— concurrency primitive that serialisesIAggregateScopedCommanddispatch per bucket id. Used by message-bus consumers (e.g. theMediatorCommandWorkerinStratara.Outbox.RabbitMQ) to keep aggregate writes single-writer.
Pipeline behavior contract
Behaviors run outer-to-inner in DI registration order:
public sealed class LoggingBehavior<TRequest, TResult> : IPipelineBehavior<TRequest, TResult>
where TRequest : IRequest<TResult>
{
public async Task<TResult> HandleAsync(
TRequest request, Func<Task<TResult>> next, CancellationToken cancellationToken)
{
// before
var result = await next();
// after
return result;
}
}
Tenant isolation
AddStrataraTenantIsolation() registers a pipeline behavior that enforces tenant isolation at the
mediator entrance — before the handler runs — for any request that opts in by implementing the
ITenantScopedRequest marker. Requests that do not implement the marker pass through untouched.
public sealed record GetCustomerQuery(Guid CustomerId, Guid TenantId)
: IQuery<CustomerDto>, ITenantScopedRequest;
services
.AddStrataraValidation() // validation stays outermost
.AddStrataraTenantIsolation(); // then tenant isolation
The behavior compares the request's TenantId (the data owner) against the ambient session's
data-owner tenant (SessionContext.TenantId), not the actor tenant (SessionContext.ActorTenantId).
A request whose payload names a different tenant than the established session subject is rejected with
TenantAccessDeniedException (translated to HTTP 403 on ASP.NET hosts that register
AddStrataraProblemDetails() from Stratara.ServiceDefaults.AspNetCore, or 401 for a caller that is not authenticated; surfaced through the
message-failure path on workers).
Default vs. strict mode
TenantIsolationMode.Default— enforces only the subject match. A privileged cross-tenant operation (actor tenant ≠ data-owner tenant) passes, because the calling endpoint is expected to have promoted the session's data-owner tenant to the target before dispatch.TenantIsolationMode.Strict— additionally routes every cross-tenant operation through anICrossTenantAuthorizer. Stratara registers a deny-all default (viaTryAdd), so strict mode rejects all cross-tenant access until you register your own authorizer that grants it:
services.AddStrataraTenantIsolation(o => o.Mode = TenantIsolationMode.Strict);
services.AddScoped<ICrossTenantAuthorizer, PlatformAdminCrossTenantAuthorizer>();
internal sealed class PlatformAdminCrossTenantAuthorizer(IHttpContextAccessor http)
: ICrossTenantAuthorizer
{
public ValueTask<bool> IsCrossTenantAllowedAsync(SessionContext session, CancellationToken ct) =>
ValueTask.FromResult(http.HttpContext?.User.IsInRole("PlatformAdmin") ?? false);
}
The behavior runs both in-process (queries via
IMediatorat the endpoint, whereHttpContextis available) and worker-side (commands dispatched through the outbox, where there is noHttpContext). AnICrossTenantAuthorizerthat needs request-role state should be applied on the in-process path; the worker path must base its decision on theSessionContextalone.
Dependencies
Stratara.Abstractions— forIMediator/IRequest/ICommand/IQuery/IPipelineBehaviorcontracts, plusITenantScopedRequest/ICrossTenantAuthorizer/TenantAccessDeniedException.Stratara.Diagnostics— log-event IDs for the tenant-isolation behavior.Microsoft.Extensions.DependencyInjection.Abstractions.Microsoft.Extensions.Logging.Abstractions.OpenTelemetry.Api— emits anActivityper dispatch under theStratara.Applicationsource.
No EF Core, no message bus, no event sourcing. Library-safe.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- JetBrains.Annotations (>= 2026.2.0)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.13)
- Microsoft.Extensions.Hosting.Abstractions (>= 10.0.13)
- Microsoft.Extensions.Logging.Abstractions (>= 10.0.13)
- Microsoft.Extensions.Options (>= 10.0.13)
- OpenTelemetry.Api (>= 1.20.1)
- Stratara.Abstractions (>= 4.7.0)
- Stratara.Diagnostics (>= 4.7.0)
NuGet packages (3)
Showing the top 3 NuGet packages that depend on Stratara.Mediator:
| Package | Downloads |
|---|---|
|
Stratara.Validation
Vendor-neutral request validation for the Stratara framework — a mediator pipeline behavior that runs IValidator<T> implementations before the handler and throws an aggregated StrataraValidationException on failure. No FluentValidation dependency; an optional adapter is shipped separately. |
|
|
Stratara.Outbox.RabbitMQ
Outbox-pattern command and event dispatch for the Stratara event-sourced stack — RabbitMQ IMessageBus implementation, retry worker, mediator command worker, and Redis-coordinated projection-replay state. Azure Service Bus support ships as the sibling Stratara.Outbox.AzureServiceBus package. |
|
|
Stratara.Infrastructure
Infrastructure glue for the Stratara framework — authorization decorators, configuration providers, and DI composition helpers that wire Mediator, Outbox, Identity, and EF Core into a hosted app. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.8.0 | 269 | 11/6/2026 |
| 4.7.1 | 188 | 11/5/2026 |
| 4.7.0 | 604 | 10/30/2026 |
| 4.6.1 | 159 | 10/29/2026 |
| 4.6.0 | 251 | 10/28/2026 |
| 4.5.0 | 326 | 10/28/2026 |
| 4.4.10 | 269 | 10/26/2026 |
| 4.4.9 | 159 | 10/26/2026 |
| 4.4.8 | 308 | 10/24/2026 |
| 4.4.7 | 172 | 10/23/2026 |
| 4.4.6 | 272 | 10/22/2026 |
| 4.4.5 | 746 | 10/14/2026 |
| 4.4.4 | 443 | 10/10/2026 |
| 4.4.3 | 185 | 10/10/2026 |
| 4.4.2 | 521 | 10/2/2026 |
| 4.4.1 | 478 | 9/29/2026 |
| 4.4.0 | 201 | 9/27/2026 |
| 4.3.1 | 189 | 9/25/2026 |
| 4.3.0 | 452 | 9/23/2026 |
| 4.2.0 | 219 | 9/18/2026 |
A release for one person who belongs to several tenants — and, sharing one identity store, to several applications.
### Added
- **`MembershipStatus.Former`** records a member who has left. It confers nothing — no role, permission or
cross-tenant access, never the tenant at sign-in, never a selection — and stays listed until the user's or the
tenant's erasure removes it.
- **`AddCheckedMembershipTenantClaim<TUser>()`**, a third tenant-claim mode: the claim is stamped at sign-in, kept when
the security-stamp validator refreshes a cookie sign-in, and checked on every request. A request whose user is no
longer an active member of the carried tenant loses the claim and resolves to the reserved default tenant, without
another tenant substituted. Only principals ASP.NET Identity issued are checked; an API key or a token the host
mints keeps its tenant. The tenant changes only when the host re-issues the sign-in. Combining it with
`AddMembershipTenantClaimsTransformation()` throws, and a claims transformation of the host's own registered
beside it is refused at start. Use it where several applications share one identity store:
`active_tenant` holds one selection per account, so live resolution moves every open session when any of them
switches.
- **`EventSubject.ForUser(userId)`** and **`EventSubject.NamesAnOwner`**: a stream can be created for a user alone,
for data that belongs to a person rather than to any of their tenants. It is recorded under the reserved default
tenant, keeps that owner for every later event whatever tenant the session names, and its encrypted fields — at
every level — are keyed to the person: shredded by the person's erasure, untouched by any tenant's.
`KeySubject.User` covers those keys too, so nothing is encrypted for the person again after the erasure.
- **`StrataraIdentityStore`, an identity store several hosts can share on PostgreSQL**, with its migrations shipped
in `Stratara.EventSourcing.EntityFrameworkCore`. It holds ASP.NET Identity's tables, passkeys included, and the
tenant directory in the fixed schema `stratara_identity`, with the history in
`stratara_identity.__stratara_identity_migrations`. `AddStrataraIdentityStore()` registers it on the connection
string `identitydb` (falling back to `defaultdb`, never through a tenant-routing `IDbResolver`) with the
directory's stores over it, and refuses a host that turns on `Stores.ProtectPersonalData`;
`MigrateStrataraIdentityStoreAsync()` creates the database where needed and applies the migrations — hosts that
migrate at once take turns. The account type is `IdentityUser` and cannot be extended, and the store fixes the
ASP.NET Identity schema version and key lengths, so every host's model matches the shipped migrations. Within a
major version the schema changes only additively. Moving an existing identity store onto it means replacing it and
seeding with the same user and tenant ids; the new guide *Shared Identity Store* describes it.
### Changed
- **Setting a membership to a status other than `Active` clears a selection that pointed at it**, as removing it
already did.
- **An explicit subject that names a user and no tenant is accepted** by `AppendOnBehalfOfAsync` and
`CreateOnBehalfOfAsync`; one that names neither is refused as before. A session whose tenant resolved to the
reserved default still gives an event no owner.
- **BREAKING (behaviour): an event or aggregate type marked `[EncryptData]` as a whole stops the host from starting.**
`EncryptionMetadataDriftGuard` refuses every registered aggregate, and every event type a registered aggregate
applies, that carries the attribute on the type; an event type no aggregate applies is refused when it is appended,
before anything is written. Once its subject was erased such a payload had nothing left to deliver, and a replay or
rebuild stopped there for good. Mark the properties instead; payloads already written as a whole are still read.
Commands and other types may still be marked as a whole.
### Fixed
- **A user's erasure shreds their own data through a key store that cannot list its scopes.** The eraser names the
user's keys under the reserved default tenant itself, at every level; until now only a listing reached the
user-level one.