Stratara.EventSourcing.WorkerDefaults 3.1.1

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher. 
dotnet add package Stratara.EventSourcing.WorkerDefaults --version 3.1.1
                    


                    

                
NuGet\Install-Package Stratara.EventSourcing.WorkerDefaults -Version 3.1.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="3.1.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Stratara.EventSourcing.WorkerDefaults" Version="3.1.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 3.1.1
                    


                    

                
#r "nuget: Stratara.EventSourcing.WorkerDefaults, 3.1.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@3.1.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=3.1.1
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Stratara.EventSourcing.WorkerDefaults&version=3.1.1
                    


                            Install as a Cake Tool

Stratara.EventSourcing.WorkerDefaults

License: FSL-1.1-MIT (Functional Source License — source-available; converts to MIT after 2 years). Not OSI-approved OSS.

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 Common + mediator + mediator-worker (hosted service that consumes the command topic into the in-process mediator) + write store + event sourcing + outbox dispatcher.
AddEventProjectionWorkerServices Common + write store + projection-replay state + projection worker.
AddSagaWorkerServices Common + write store + event sourcing + outbox dispatcher + 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
3.1.1 50 6/1/2026
3.1.0 59 5/30/2026
3.0.23 55 5/28/2026

### Fixed

- **`FileMasterKeyProvider` now rejects a master KEK that is not exactly 32 bytes at startup.**
 The KEK is used directly as an AES-256-GCM key, which accepts only 16/24/32-byte keys. The
 provider previously required merely *at least* 32 bytes, so a longer KEK (for example the
 48-byte output of `openssl rand -base64 48`, a common HKDF master-key recipe) passed both
 construction and the eager `FileKeyStoreStartupProbe`, then threw
 `CryptographicException: Specified key is not a valid size for this algorithm` on the **first**
 key creation at runtime — defeating the purpose of the boot-time probe. The provider now
 validates the decoded length is exactly 32 bytes and fails fast at boot with an actionable
 message (`Generate one with: openssl rand -base64 32`). A 32-byte KEK is unaffected.
- **`EnvelopeFileKeyStore` is now safe for multiple processes sharing one store file** (for
 example several containers bind-mounting the same host directory). Previously a process only
 read the store once at construction, so a data-encryption key created by another process after
 startup was invisible (`GetDataEncryptionKeyAsync` returned `null`, breaking decryption), and
 two processes creating keys concurrently could overwrite each other's keys or mint colliding
 versions for the same scope. Reads now reload from disk on a cache miss (guarded by the file's
 last-write time to avoid reload storms), and every mutation serializes through an exclusive
 cross-process lock file and re-reads the latest on-disk state before writing. A networked file
 system (NFS/SMB) remains unsupported — it guarantees neither atomic rename nor reliable advisory
 locks.

### Added

- **`LogEvents.KeyManagement.KeyStoreReloaded` (112_006)** — debug-level event emitted when the
 file key store reloads its state from disk to pick up keys written by another process.