Stratara.Projections
3.2.2
dotnet add package Stratara.Projections --version 3.2.2
NuGet\Install-Package Stratara.Projections -Version 3.2.2
<PackageReference Include="Stratara.Projections" Version="3.2.2" />
<PackageVersion Include="Stratara.Projections" Version="3.2.2" />
<PackageReference Include="Stratara.Projections" />
paket add Stratara.Projections --version 3.2.2
#r "nuget: Stratara.Projections, 3.2.2"
#:package Stratara.Projections@3.2.2
#addin nuget:?package=Stratara.Projections&version=3.2.2
#tool nuget:?package=Stratara.Projections&version=3.2.2
Stratara.Projections
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 |
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 (>= 2025.2.4)
- Microsoft.Extensions.Hosting.Abstractions (>= 10.0.8)
- Microsoft.Extensions.Options.ConfigurationExtensions (>= 10.0.8)
- Stratara.Contracts (>= 3.2.2)
- Stratara.Domain (>= 3.2.2)
- Stratara.Shared (>= 3.2.2)
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, AddHeavyCommandWorkerServices, AddEventProjectionWorkerServices, AddEventStreamHashWorkerServices, 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.
API keys can now be bootstrapped. Issuance always generated the key itself, which does not fit the
setups where server and caller have to share a key *before* either starts — container orchestration,
CI provisioning, self-hosted bundles, end-to-end test hosts. This release adds an import path for a
key the caller already holds, plus the canonical key format as public API so callers generate values
instead of inventing them.
### Added
- **`IApiKeyStore.ImportAsync` — store a machine key whose raw value the caller already holds.**
Issuance generates the key itself, which is the wrong shape when server and caller must share it
*before* either boots: container orchestration, CI provisioning, self-hosted bundles, end-to-end
test hosts. Without this path, consumers bypassed the store and reimplemented its internals (the
digest format and the machine-key membership row) — a copy that keeps compiling after the store
changes and fails as a runtime 401. Import is idempotent, so it can run unconditionally on every
boot: a value that is already stored returns the existing descriptor and the stored key is never
mutated, so a changed configuration cannot escalate a key's roles or extend its expiry unnoticed.
Revoked, expired, and foreign-tenant values are rejected rather than silently adopted, and
concurrent replicas racing the same first import converge on one key. Machine keys only —
`ApiKeyImportRequest` carries no `UserId`.
- **`ApiKeyFormat` (`Stratara.Abstractions.ApiKeys`) — the canonical raw-key format as public API.**
`CreateRawKey()` generates `stk_` plus the Base64Url encoding of 32 CSPRNG bytes; `IsWellFormed()`
checks that shape. `ImportAsync` accepts only well-formed values: the store keeps its stored
digest unsalted because a generated key carries 256 bits of entropy, and a hand-picked value would
quietly invalidate that. Generate keys out of band with `CreateRawKey()` and keep them in a secret
store — the type lives in the abstractions package so host-builder and orchestration projects can
reach it without referencing the storage implementation.
- **`InMemoryApiKeyStore` (`Stratara.Testing`) — the drop-in double for the API-key store**,
mirroring issuance, import, fail-closed validation, revocation, and the erasure sweeps, and
materializing machine keys into a membership store you can share and inspect.
### Changed
- **API-key lifecycle events are now logged** (`Stratara.Diagnostics` event-ID range 116_000):
import, idempotent repeat, and a repeat that supplied different parameters. Key ids and tenant
ids only — never the raw key or its digest.
- **For implementers of `IApiKeyStore`:** the interface gained `ImportAsync`. Custom implementations
need the new member; callers are unaffected.