Stratara.EventSourcing.WorkerDefaults 4.7.1

Prefix Reserved
dotnet add package Stratara.EventSourcing.WorkerDefaults --version 4.7.1
                    
NuGet\Install-Package Stratara.EventSourcing.WorkerDefaults -Version 4.7.1
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Stratara.EventSourcing.WorkerDefaults" Version="4.7.1" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Stratara.EventSourcing.WorkerDefaults" Version="4.7.1" />
                    
Directory.Packages.props
<PackageReference Include="Stratara.EventSourcing.WorkerDefaults" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Stratara.EventSourcing.WorkerDefaults --version 4.7.1
                    
#r "nuget: Stratara.EventSourcing.WorkerDefaults, 4.7.1"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Stratara.EventSourcing.WorkerDefaults@4.7.1
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Stratara.EventSourcing.WorkerDefaults&version=4.7.1
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.EventSourcing.WorkerDefaults&version=4.7.1
                    
Install as a Cake Tool

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 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

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.7.1 0 11/5/2026
4.7.0 352 10/30/2026
4.6.1 84 10/29/2026
4.6.0 163 10/28/2026
4.5.0 252 10/28/2026
4.4.10 203 10/26/2026
4.4.9 104 10/26/2026
4.4.8 251 10/24/2026
4.4.7 111 10/23/2026
4.4.6 210 10/22/2026
4.4.5 286 10/14/2026
4.4.4 289 10/10/2026
4.4.3 120 10/10/2026
4.4.2 387 10/2/2026
4.4.1 369 9/29/2026
4.4.0 148 9/27/2026
4.3.1 143 9/25/2026
4.3.0 302 9/23/2026
4.2.0 187 9/18/2026
4.1.1 113 9/16/2026
Loading failed

A patch for the shared identity store: single roles of a membership can now change without losing a concurrent
change, and a fresh store's first migration no longer logs a spurious error.

### Added

- **`ITenantMembershipStore.AddRolesAsync` and `RemoveRolesAsync`** give or take single roles of one membership,
 leaving its other roles and its status as they are, and return the membership afterwards (`null` where there is
 none — neither creates one). On the framework's stores two overlapping role changes to the same membership both
 take effect; a store that keeps losing to concurrent writers throws `InvalidOperationException` instead of dropping
 the change. No schema change. Both are default interface methods, so a store you implemented yourself keeps
 compiling and gets them as a read followed by a whole write — without protection against a concurrent writer.
 `TenantMembership.WithRolesAdded` and `WithRolesRemoved` compute the changed role set.

### Fixed

- **`MigrateStrataraIdentityStoreAsync()` no longer logs an `Error` on a fresh database.** The first migration of an
 empty identity store logged a failed read of its migration history table from
 `Microsoft.EntityFrameworkCore.Database.Command`, although the migration then succeeded. The database, the schema and
 the history table are now created before the migrations run, so a first start logs nothing at `Error` or above —
 also when several hosts start against an empty store at once.