Stratara.EventSourcing.WorkerDefaults
4.4.9
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.EventSourcing.WorkerDefaults --version 4.4.9
NuGet\Install-Package Stratara.EventSourcing.WorkerDefaults -Version 4.4.9
<PackageReference Include="Stratara.EventSourcing.WorkerDefaults" Version="4.4.9" />
<PackageVersion Include="Stratara.EventSourcing.WorkerDefaults" Version="4.4.9" />
<PackageReference Include="Stratara.EventSourcing.WorkerDefaults" />
paket add Stratara.EventSourcing.WorkerDefaults --version 4.4.9
#r "nuget: Stratara.EventSourcing.WorkerDefaults, 4.4.9"
#:package Stratara.EventSourcing.WorkerDefaults@4.4.9
#addin nuget:?package=Stratara.EventSourcing.WorkerDefaults&version=4.4.9
#tool nuget:?package=Stratara.EventSourcing.WorkerDefaults&version=4.4.9
Stratara.EventSourcing.WorkerDefaults
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
License: MIT.
One-stop IHostApplicationBuilder composites that wire together the Stratara event-sourced stack for each host shape (API, command worker, event-projection worker, saga worker, event-stream-hash worker, outbox worker). Reference this package from each host instead of repeating the per-concern DI call chain.
What's in the box
| Composite | Wires |
|---|---|
AddBackendServices |
Common framework services (messaging, identity, session, security, mapping, resilience) + mediator + write store + outbox dispatcher. For API hosts that dispatch commands but don't process them. |
AddCommandWorkerServices |
AddCommandServices + mediator-worker (hosted service that consumes the command topic into the in-process mediator). |
AddCommandServices |
Common + mediator + write store + event sourcing + outbox dispatcher, without the mediator worker. For command silos of the Orleans execution model. |
AddEventProjectionWorkerServices |
Common + write store + projection-replay state + projection worker. |
AddEventProjectionServices |
The same without the bus-fed projection worker. |
AddSagaWorkerServices |
Common + write store + event sourcing + outbox dispatcher + saga worker. |
AddSagaServices |
The same without the bus-fed saga worker. |
AddEventStreamHashWorkerServices |
Common + write store + event-stream-hashing worker. |
AddOutboxWorkerServices |
Common + write store + outbox dispatcher + outbox-retry worker. |
The composites live in the Microsoft.Extensions.Hosting namespace so call sites read naturally:
// Command-handling worker host:
builder.AddCommandWorkerServices();
// API host that only dispatches commands:
builder.AddBackendServices();
Dependencies
This package pulls the framework's Tier-C pieces (Stratara.Infrastructure, Stratara.Outbox.RabbitMQ, Stratara.Projections, Stratara.Sagas, Stratara.EventSourcing.EntityFrameworkCore) so a single PackageReference is enough for a worker host. The lean Stratara.ServiceDefaults (OTel + Serilog) and Stratara.ServiceDefaults.AspNetCore (health-check endpoints + ASP.NET OTel) stay separate so non-worker hosts don't drag the Tier-C runtime in.
| 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
- Stratara.EventSourcing.EntityFrameworkCore (>= 4.4.9)
- Stratara.Infrastructure (>= 4.4.9)
- Stratara.Outbox.RabbitMQ (>= 4.4.9)
- Stratara.Projections (>= 4.4.9)
- Stratara.Sagas (>= 4.4.9)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.8.0 | 98 | 11/6/2026 |
| 4.7.1 | 104 | 11/5/2026 |
| 4.7.0 | 420 | 10/30/2026 |
| 4.6.1 | 96 | 10/29/2026 |
| 4.6.0 | 165 | 10/28/2026 |
| 4.5.0 | 254 | 10/28/2026 |
| 4.4.10 | 204 | 10/26/2026 |
| 4.4.9 | 105 | 10/26/2026 |
| 4.4.8 | 254 | 10/24/2026 |
| 4.4.7 | 113 | 10/23/2026 |
| 4.4.6 | 213 | 10/22/2026 |
| 4.4.5 | 287 | 10/14/2026 |
| 4.4.4 | 291 | 10/10/2026 |
| 4.4.3 | 123 | 10/10/2026 |
| 4.4.2 | 389 | 10/2/2026 |
| 4.4.1 | 371 | 9/29/2026 |
| 4.4.0 | 149 | 9/27/2026 |
| 4.3.1 | 144 | 9/25/2026 |
| 4.3.0 | 304 | 9/23/2026 |
| 4.2.0 | 191 | 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.