Stratara.Infrastructure 4.4.8

Prefix Reserved
.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package Stratara.Infrastructure --version 4.4.8
                    


                    

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


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Stratara.Infrastructure" />
                    


                            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.Infrastructure --version 4.4.8
                    


                    

                
#r "nuget: Stratara.Infrastructure, 4.4.8"
#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.Infrastructure@4.4.8
#: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.Infrastructure&version=4.4.8
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Stratara.Infrastructure&version=4.4.8
                    


                            Install as a Cake Tool

Stratara.Infrastructure

Derived. The behaviour described here is specified under openspec/specs/. Those specifications are the source; this page explains and illustrates them.

License: MIT.

Cross-cutting infrastructure plumbing for the Stratara framework — the Tier-C glue that lets downstream apps wire authorization, DI composition, and worker-stack configuration with a single reference.

Contents

  • Authorization decorators over command-outbox dispatch (AuthorizingCommandOutboxDispatcher) — enforces [RequireRole] and [RequirePermission] on the command's runtime type before it reaches the outbox.
  • DI composition helpers that wire Mediator, Outbox, Identity, and EFCore into a hosted app.
  • Configuration providers and option binders used by the worker stack.

Dependencies

Transitively depends on Stratara.Contracts, Stratara.EventSourcing.EntityFrameworkCore, Stratara.Mediator, Stratara.Outbox.RabbitMQ, Stratara.Sessions, Stratara.Shared.

Behavioural notes

AddSecurity() — IKeyStore registration (since 3.0.11)

AddSecurity() registers Stratara's security stack including the IKeyStore abstraction. The default is a TryAddSingleton<IKeyStore, DummyKeyStore> fallback — but DummyKeyStore since 3.0.11 throws InvalidOperationException in any environment other than Development (whitelist guard to prevent production data exposure from the demo encryption key). Hosts on Staging, QA, UAT, Preview, or any custom environment must register a real IKeyStore implementation before calling AddSecurity():

// Recommended composition root
if (builder.Environment.IsDevelopment())
{
    builder.Services.AddSecurity();   // DummyKeyStore fallback is fine
}
else
{
    // The production key store Stratara ships (Stratara.Security): KEK-wrapped, versioned
    // per-scope DEKs. Register it before AddSecurity() so it wins the TryAdd race.
    builder.Services.AddStrataraFileKeyStore(builder.Configuration);
    builder.Services.AddSecurity();
}

Stratara ships one production IKeyStore — EnvelopeFileKeyStore, via AddStrataraFileKeyStore. There is no built-in Azure Key Vault / AWS KMS / HSM store; if you need one, implement IKeyStore against your provider and register it in place of the file store. Implement ListScopesAsync as well: an erasure asks the key store for every key naming the subject, and a store that cannot list leaves it with only the keys the directory names.

KeyStoreStartupProbe logs a Warning (event id LogEvents.KeyManagement.DummyKeyStoreActive = 112_001) at host start when the resolved IKeyStore is DummyKeyStore — even in Development — so an accidental dependency on the dummy is loud rather than silent.

Why the change: Before 3.0.11 the guard only blocked IsProduction(). Hosts in any other environment silently encrypted with the world-known constant pass-phrase "StrataraTestKey" baked into the shipping NuGet — a Staging or QA copy of production data could be decrypted by anyone reading the source. The whitelist guard makes this configuration crash-fast at host build instead of allowing silent data exposure.

AddCaching() — Redis registration

AddCaching() used to delegate to builder.AddRedisClient("redis") from Aspire.StackExchange.Redis. After the Aspire-wrapper removal it registers IConnectionMultiplexer directly via ConnectionMultiplexer.Connect(...) from StackExchange.Redis. The method signature is unchanged, but the Aspire-only side-effects are gone:

  • No automatic Redis health check. Add one explicitly with AddHealthChecks().AddRedis(connectionString) (from AspNetCore.HealthChecks.Redis) if your host exposes /health and you want Redis covered.
  • No automatic OpenTelemetry Redis instrumentation. Add OpenTelemetry.Instrumentation.StackExchangeRedis and .AddRedisInstrumentation() to your TracerProviderBuilder if you want Redis spans in your traces.

The connection-string lookup (ConnectionStrings:redis in configuration) is identical to the pre-cleanup behaviour.

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 (2)

Showing the top 2 NuGet packages that depend on Stratara.Infrastructure:

Package Downloads
Stratara.EventSourcing.WorkerDefaults

Worker-host wiring composites for the Stratara event-sourced stack. IHostApplicationBuilder extensions (AddBackendServices, AddCommandWorkerServices, AddHeavyCommandWorkerServices, AddEventProjectionWorkerServices, AddEventStreamHashWorkerServices, AddSagaWorkerServices, AddOutboxWorkerServices, and AddCommandServices, AddEventProjectionServices and AddSagaServices without the bus-fed workers) bundle the per-concern DI calls so each worker host opts in with one line.
Stratara.Testing.EntityFrameworkCore

Spin up the real Stratara event-sourcing write stack (EventSource, aggregation, snapshots, the EF Core write store) against a shared in-memory SQLite database in one call — production code paths, no Postgres, no Docker. Builds on Stratara.Testing's in-memory doubles.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
4.8.0 97 11/6/2026
4.7.1 97 11/5/2026
4.7.0 457 10/30/2026
4.6.1 128 10/29/2026
4.6.0 195 10/28/2026
4.5.0 280 10/28/2026
4.4.10 230 10/26/2026
4.4.9 131 10/26/2026
4.4.8 279 10/24/2026
4.4.7 140 10/23/2026
4.4.6 243 10/22/2026
4.4.5 319 10/14/2026
4.4.4 316 10/10/2026
4.4.3 151 10/10/2026
4.4.2 418 10/2/2026
4.4.1 404 9/29/2026
4.4.0 161 9/27/2026
4.3.1 160 9/25/2026
4.3.0 322 9/23/2026
4.2.0 202 9/18/2026
Loading failed

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.