Stratara.EventSourcing.WorkerDefaults
4.4.8
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.EventSourcing.WorkerDefaults --version 4.4.8
NuGet\Install-Package Stratara.EventSourcing.WorkerDefaults -Version 4.4.8
<PackageReference Include="Stratara.EventSourcing.WorkerDefaults" Version="4.4.8" />
<PackageVersion Include="Stratara.EventSourcing.WorkerDefaults" Version="4.4.8" />
<PackageReference Include="Stratara.EventSourcing.WorkerDefaults" />
paket add Stratara.EventSourcing.WorkerDefaults --version 4.4.8
#r "nuget: Stratara.EventSourcing.WorkerDefaults, 4.4.8"
#:package Stratara.EventSourcing.WorkerDefaults@4.4.8
#addin nuget:?package=Stratara.EventSourcing.WorkerDefaults&version=4.4.8
#tool nuget:?package=Stratara.EventSourcing.WorkerDefaults&version=4.4.8
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.8)
- Stratara.Infrastructure (>= 4.4.8)
- Stratara.Outbox.RabbitMQ (>= 4.4.8)
- Stratara.Projections (>= 4.4.8)
- Stratara.Sagas (>= 4.4.8)
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 | 95 | 11/6/2026 |
| 4.7.1 | 103 | 11/5/2026 |
| 4.7.0 | 418 | 10/30/2026 |
| 4.6.1 | 95 | 10/29/2026 |
| 4.6.0 | 164 | 10/28/2026 |
| 4.5.0 | 253 | 10/28/2026 |
| 4.4.10 | 203 | 10/26/2026 |
| 4.4.9 | 104 | 10/26/2026 |
| 4.4.8 | 253 | 10/24/2026 |
| 4.4.7 | 112 | 10/23/2026 |
| 4.4.6 | 212 | 10/22/2026 |
| 4.4.5 | 286 | 10/14/2026 |
| 4.4.4 | 289 | 10/10/2026 |
| 4.4.3 | 122 | 10/10/2026 |
| 4.4.2 | 387 | 10/2/2026 |
| 4.4.1 | 370 | 9/29/2026 |
| 4.4.0 | 148 | 9/27/2026 |
| 4.3.1 | 143 | 9/25/2026 |
| 4.3.0 | 303 | 9/23/2026 |
| 4.2.0 | 190 | 9/18/2026 |
A fix for hosts on the Orleans execution model. A store reader that catches up a large backlog and a singleton
work that runs long now answer their keep-alive, so neither leaves reminder errors in the silo's log. A silo that
joins while a singleton work runs long on another silo no longer fails its start. No API change, no schema change
and no migration.
### Fixed
- **A busy store reader or singleton work answers its keep-alive.** On the Orleans execution model, a projection or
saga reader that caught up a backlog for longer than the runtime's response timeout made its keep-alive tick wait
behind the catch-up, and Orleans logged `Could not deliver reminder tick` at Error, once per partition and
keep-alive period. A singleton work whose run outlasted the timeout did the same. Nothing was lost, but a large
catch-up left dozens of errors on the silo. The keep-alive and the poll now start a catch-up where none is
running and do not wait for it. A partition is still read by one catch-up at a time, and a commit during a
catch-up is still applied by it. A singleton work's keep-alive interleaves with its run, and runs still never
overlap.
- **A silo starts while a singleton work runs long.** A silo that started while a singleton work it registers ran
longer than the response timeout on another silo waited for that run in its own start. The start then failed
with a `TimeoutException`. The call a starting silo makes to each singleton work and store reader now
interleaves, so the start goes on.
- *Operate the Orleans execution model* says that a durable timer whose handler outlasts the response timeout
still makes Orleans log `Could not deliver reminder tick` for that tick, and that the line says nothing about
the timer. It also says that, outside a deploy, the line now points to an unreachable store reader or singleton
work rather than a busy one.