Stratara.Projections
4.4.10
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Projections --version 4.4.10
NuGet\Install-Package Stratara.Projections -Version 4.4.10
<PackageReference Include="Stratara.Projections" Version="4.4.10" />
<PackageVersion Include="Stratara.Projections" Version="4.4.10" />
<PackageReference Include="Stratara.Projections" />
paket add Stratara.Projections --version 4.4.10
#r "nuget: Stratara.Projections, 4.4.10"
#:package Stratara.Projections@4.4.10
#addin nuget:?package=Stratara.Projections&version=4.4.10
#tool nuget:?package=Stratara.Projections&version=4.4.10
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.10)
- Stratara.Domain (>= 4.4.10)
- Stratara.Shared (>= 4.4.10)
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 | 271 | 11/6/2026 |
| 4.7.1 | 199 | 11/5/2026 |
| 4.7.0 | 597 | 10/30/2026 |
| 4.6.1 | 167 | 10/29/2026 |
| 4.6.0 | 236 | 10/28/2026 |
| 4.5.0 | 323 | 10/28/2026 |
| 4.4.10 | 268 | 10/26/2026 |
| 4.4.9 | 174 | 10/26/2026 |
| 4.4.8 | 321 | 10/24/2026 |
| 4.4.7 | 176 | 10/23/2026 |
| 4.4.6 | 282 | 10/22/2026 |
| 4.4.5 | 367 | 10/14/2026 |
| 4.4.4 | 349 | 10/10/2026 |
| 4.4.3 | 183 | 10/10/2026 |
| 4.4.2 | 445 | 10/2/2026 |
| 4.4.1 | 433 | 9/29/2026 |
| 4.4.0 | 187 | 9/27/2026 |
| 4.3.1 | 192 | 9/25/2026 |
| 4.3.0 | 357 | 9/23/2026 |
| 4.2.0 | 231 | 9/18/2026 |
A release for hosts on the Orleans execution model. A durable timer now answers its tick while its handler runs, so a
long handler leaves no reminder error in the silo's log, and a timer that fails is logged by the framework with its
owner and purpose. A commit no longer constructs every registered projection to learn which store readers to wake. No
API change, no schema change and no migration.
### Changed
- **A commit no longer constructs every projection.** On the Orleans execution model, every command that committed
facts constructed each registered projection, with its dependencies, only to learn the names of the store readers to
wake. The names are now worked out once per silo, and the wait for a projection, the rebuild and the full replay's
checkpoint reset use the same list. A rebuild of a name that is not registered is refused before any reader is
paused, with the same message as before.
### Fixed
- **A durable timer answers its tick while its handler runs.** On the Orleans execution model, a durable timer's
reminder call stayed open until its handler returned, so a handler longer than the runtime's response timeout made
Orleans log `Could not deliver reminder tick` at Error for every tick it outlasted. The tick is now answered at once
and the handler runs in a call that carries no response timeout. The timer still fires once per due time, a tick
during its handler still does nothing, and a handler stopped with its silo still fires again on the next one.
- **A failing timer is logged.** A durable timer whose handler threw — or whose owner check or unregistration
failed — was visible only as Orleans' reminder error line. It is now logged as `117_137` `TimerFiringFailed` (Error)
with the owner, the purpose and the exception, and the timer fires again after its retry period as before.