Stratara.Projections
4.4.9
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Projections --version 4.4.9
NuGet\Install-Package Stratara.Projections -Version 4.4.9
<PackageReference Include="Stratara.Projections" Version="4.4.9" />
<PackageVersion Include="Stratara.Projections" Version="4.4.9" />
<PackageReference Include="Stratara.Projections" />
paket add Stratara.Projections --version 4.4.9
#r "nuget: Stratara.Projections, 4.4.9"
#:package Stratara.Projections@4.4.9
#addin nuget:?package=Stratara.Projections&version=4.4.9
#tool nuget:?package=Stratara.Projections&version=4.4.9
Stratara.Projections
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
License: MIT.
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/ |
The runtime, all internal: ProjectionManager (event-bundle → matching projection-handlers fan-out), ProjectionHandler (invokes a projection's matching methods), ProjectionMethodInvoker (reflection-cached method-pointer dispatch into consumer projections). You implement IProjection; these drive it |
Abstractions/ |
IProjection and its refinements: IRebuildableProjection (can be rebuilt alone on the Orleans execution model) and IForgetsDeletedTenants (a fact recorded for a tenant after its deletion is passed over instead of failing the projection; the record is kept by IForgottenTenantStore, which the read store provides), and IReadModelPreservation (lets a failed replay restore the read models it emptied; the PostgreSQL implementation comes with AddReadModelRestore<TReadContext>()) |
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
.AddProjectionWorker(builder.Configuration) // the runtime + hosted service
.AddProjectionsFromAssemblyContaining<MyAppProjectionMarker>(); // your IProjection implementations
Then implement IProjection in your application assembly. The projection manager picks them up automatically.
Both calls are needed: AddProjectionsFromAssemblyContaining<T>() only registers your projections —
AddProjectionWorker(IConfiguration) registers the manager, the invoker and the hosted service that
consumes the event-bundle subscription. Without it nothing drives your projections. Most hosts get
both from the AddEventProjectionWorkerServices() composite in Stratara.EventSourcing.WorkerDefaults.
No checkpoint store. Projections are driven push-wise off the event bus; the framework keeps no per-projection checkpoint, so there is no consumer-lag metric and no built-in resume-from-sequence. Replay is coordinated separately (see
Stratara.Outbox.RabbitMQ's replay state).
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 (>= 2026.2.0)
- Microsoft.Extensions.Hosting.Abstractions (>= 10.0.13)
- Microsoft.Extensions.Options.ConfigurationExtensions (>= 10.0.13)
- Stratara.Contracts (>= 4.4.9)
- Stratara.Domain (>= 4.4.9)
- Stratara.Shared (>= 4.4.9)
NuGet packages (3)
Showing the top 3 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 — including a shared identity store with its migrations — shared conventions, value generators, and UnitOfWork primitives. Targets Npgsql; maps pgvector types for a model that uses them, and needs no database extension otherwise. |
|
|
Stratara.EventSourcing.WorkerDefaults
Worker-host wiring composites for the Stratara event-sourced stack. IHostApplicationBuilder extensions (AddBackendServices, AddCommandWorkerServices, AddHeavyCommandWorkerServices, AddEventProjectionWorkerServices, AddEventStreamHashWorkerServices, AddSagaWorkerServices, AddOutboxWorkerServices, and AddCommandServices, AddEventProjectionServices and AddSagaServices without the bus-fed workers) bundle the per-concern DI calls so each worker host opts in with one line. |
|
|
Stratara.Orleans
The Orleans execution model for the Stratara event-sourced stack — one activation per aggregate across the cluster, commands recorded before the call returns and resumed after a crash, projections and sagas that read the store in commit order from a checkpoint, singleton work, owner-checked durable timers and heavy work bounded across the cluster. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.8.0 | 210 | 11/6/2026 |
| 4.7.1 | 177 | 11/5/2026 |
| 4.7.0 | 597 | 10/30/2026 |
| 4.6.1 | 165 | 10/29/2026 |
| 4.6.0 | 231 | 10/28/2026 |
| 4.5.0 | 321 | 10/28/2026 |
| 4.4.10 | 267 | 10/26/2026 |
| 4.4.9 | 173 | 10/26/2026 |
| 4.4.8 | 320 | 10/24/2026 |
| 4.4.7 | 174 | 10/23/2026 |
| 4.4.6 | 280 | 10/22/2026 |
| 4.4.5 | 366 | 10/14/2026 |
| 4.4.4 | 348 | 10/10/2026 |
| 4.4.3 | 182 | 10/10/2026 |
| 4.4.2 | 444 | 10/2/2026 |
| 4.4.1 | 433 | 9/29/2026 |
| 4.4.0 | 186 | 9/27/2026 |
| 4.3.1 | 191 | 9/25/2026 |
| 4.3.0 | 353 | 9/23/2026 |
| 4.2.0 | 230 | 9/18/2026 |
A fix for hosts on the Orleans execution model. A host that removed or renamed a projection no longer has that
projection's store readers come back on every start and fail each entry; they retire once, as a saga's readers do. A
retired store reader now logs its retirement once instead of three times, and leaves no reminder error behind. No
API change, no schema change and no migration.
### Fixed
- **A reader of a removed projection retires.** On the Orleans execution model, a host that removed or renamed a
projection kept the keep-alive reminders of its store readers. On every start of the silo they brought the readers
back, and each one read the next entry of its partition, failed it because no projection of its name was
registered, and tried again on the next tick, without end — a warning per partition and entry. Such a reader now
retires the first time it is brought back, as a saga's reader already did: it unregisters its keep-alive, logs
`117_136` `UnregisteredProjectionReaderRetired` (Information) once, reads nothing and deactivates. Its checkpoints
stay, so a projection registered again resumes where it stopped; *Operate the Orleans execution model* says how to
delete them. In a rolling deployment that adds a projection, a reader that lands on a silo of the earlier version
refuses a rebuild's or a replay's pause, which then fails naming it, and a wait counts its partition as behind.
- **A retired store reader logs its retirement once.** A reader that retired as it was activated — of a partition
beyond a lowered partition count, or of a saga the silo no longer registers — deactivated before it answered the
call that activated it. Orleans forwarded that call to a new activation, which retired again, so the retirement was
logged three times per reader and the keep-alive tick ended in `Could not deliver reminder tick` at Error. The
reader now answers the call first and deactivates after it.