Stratara.Projections
3.1.3
dotnet add package Stratara.Projections --version 3.1.3
NuGet\Install-Package Stratara.Projections -Version 3.1.3
<PackageReference Include="Stratara.Projections" Version="3.1.3" />
<PackageVersion Include="Stratara.Projections" Version="3.1.3" />
<PackageReference Include="Stratara.Projections" />
paket add Stratara.Projections --version 3.1.3
#r "nuget: Stratara.Projections, 3.1.3"
#:package Stratara.Projections@3.1.3
#addin nuget:?package=Stratara.Projections&version=3.1.3
#tool nuget:?package=Stratara.Projections&version=3.1.3
Stratara.Projections
License: FSL-1.1-MIT (Functional Source License — source-available; converts to MIT after 2 years). Not OSI-approved OSS.
Projection runtime for the Stratara event-sourced stack. Discovers IProjection implementations in the consumer's application assemblies, dispatches event bundles to them, and applies the resulting change sets atomically via the read-model repository layer.
What's in the box
| Folder | Contents |
|---|---|
Services/ |
ProjectionManager (event-bundle → matching projection-handlers fan-out), ProjectionHandler<TEvent> base class, ProjectionMethodInvoker (reflection-cached method-pointer dispatch into consumer projections), checkpoint plumbing |
Multitenancy/ |
TenantProjection — the framework's own opinionated tenant aggregate projection. Skip the registration if your application has its own tenancy model |
Diagnostics/Extensions/ |
Source-generated LoggerProjectionExtensions, LoggerChangeSetExtensions, LoggerUpdateExtensions — typed [LoggerMessage] surfaces under the Stratara.Projection.* / Stratara.ChangeSet.* / Stratara.Update.* event-ID bands |
Quick start
// In your EventProjection worker:
builder.Services.AddProjectionsFromAssemblyContaining<MyAppProjectionMarker>();
Then implement IProjection in your application assembly. The projection manager picks them up automatically.
Dependencies
Stratara.Contracts— forEventBundle+IEvent<T>.Stratara.Domain— for the framework'sTenantaggregate (only consumed byTenantProjection).Stratara.Shared— for change-tracking primitives, reflection cache, partitioning helpers, diagnostics base.Microsoft.Extensions.Hosting.Abstractions+Microsoft.Extensions.Options.ConfigurationExtensions— for projection-worker checkpointing options.JetBrains.Annotations— for static-analysis attributes on projection-handler conventions.
| 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 (>= 2025.2.4)
- Microsoft.Extensions.Hosting.Abstractions (>= 10.0.8)
- Microsoft.Extensions.Options.ConfigurationExtensions (>= 10.0.8)
- Stratara.Contracts (>= 3.1.3)
- Stratara.Domain (>= 3.1.3)
- Stratara.Shared (>= 3.1.3)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on Stratara.Projections:
| Package | Downloads |
|---|---|
|
Stratara.EventSourcing.EntityFrameworkCore
EF Core persistence for the Stratara event-sourced stack on PostgreSQL — write-store, read-store, ASP.NET Identity store, shared conventions, value generators, and UnitOfWork primitives. Targets Npgsql with pgvector. |
|
|
Stratara.EventSourcing.WorkerDefaults
Worker-host wiring composites for the Stratara event-sourced stack. IHostApplicationBuilder extensions (AddBackendServices, AddCommandWorkerServices, AddEventProjectionWorkerServices, AddSagaWorkerServices, AddOutboxWorkerServices) bundle the per-concern DI calls so each worker host opts in with one line. |
GitHub repositories
This package is not used by any popular GitHub repositories.
### Added
- **Mediator tenant-isolation behavior** (`Stratara.Mediator`) — `AddStrataraTenantIsolation()`
registers a pipeline behavior that enforces tenant isolation at the mediator entrance, before the
handler runs, for any request that opts in via the new `ITenantScopedRequest` marker
(`Stratara.Abstractions.Multitenancy`). The behavior compares the request's `TenantId` (data owner)
against the ambient session's data-owner tenant and rejects a mismatch with the new
`TenantAccessDeniedException` (translated to HTTP 403 on ASP.NET hosts). `TenantIsolationMode.Default`
enforces only the subject match (privileged cross-tenant operations pass when the endpoint promoted
the session subject to the target); `TenantIsolationMode.Strict` additionally routes every
cross-tenant operation through the new `ICrossTenantAuthorizer`, whose shipped default denies all
cross-tenant access until a consumer registers its own authorizer. Complements the existing
database-side `ApplyGlobalTenantQueryFilters` with a command-/query-entrance guard. New log-event
IDs `114_101`/`114_102`/`114_003` in `Stratara.Diagnostics`.
- **`Stratara.Abstractions.Persistence.ConcurrencyConflictException`** — provider-agnostic
wrapper for an optimistic-concurrency conflict detected during commit. Allows framework-level
code in `Stratara.Projections` (and any consumer outside the `EntityFrameworkCore` package) to
react to concurrency without taking an EF Core dependency. EF Core's `DbUpdateConcurrencyException`
(and provider equivalents) flow through this type.
### Changed
- **`EfTransaction.SaveChangesAsync`** (in `Stratara.EventSourcing.EntityFrameworkCore`) now
wraps `DbUpdateConcurrencyException` thrown by EF Core in the new
`ConcurrencyConflictException`. PostgreSQL unique-violation paths remain on `DbUpdateException`
(different semantics — duplicate-key on insert vs. stale-row on update/delete).
- **`EventSource.SaveChangesAsync`** (write-side append flow) extends its concurrency-handling
catch to the new exception type so the existing append-conflict recovery path keeps working
after the wrap. Behaviour for both EF concurrency conflicts and PostgreSQL unique violations
is unchanged.
### Fixed
- **`TenantProjection` no longer aborts the event bundle on a parallel delete race.** The two
delete handlers (`TenantDeleted`, `CustomerTenantsDeleted`) now swallow
`ConcurrencyConflictException` silently — a missing row is the desired end-state of a delete.
Before this fix, a consumer-side customer-delete cascade saga that emits both
`CustomerTenantsDeleted` and a follow-up `TenantDeleted` for the same tenants would race the
two parallel projection bundles on the same `TenantView` row; the loser threw
`DbUpdateConcurrencyException` out of `SaveChangesAsync`, which propagated through
`ProjectionWorker` and caused `RabbitMqBus` to roll back the entire bundle — including
sibling projections that had already committed. Update handlers (rename / activate /
deactivate / locale / customer-assigned) keep their current behaviour: a concurrency failure
there is a real race that propagates.