Stratara.Infrastructure
3.1.5
See the version list below for details.
dotnet add package Stratara.Infrastructure --version 3.1.5
NuGet\Install-Package Stratara.Infrastructure -Version 3.1.5
<PackageReference Include="Stratara.Infrastructure" Version="3.1.5" />
<PackageVersion Include="Stratara.Infrastructure" Version="3.1.5" />
<PackageReference Include="Stratara.Infrastructure" />
paket add Stratara.Infrastructure --version 3.1.5
#r "nuget: Stratara.Infrastructure, 3.1.5"
#:package Stratara.Infrastructure@3.1.5
#addin nuget:?package=Stratara.Infrastructure&version=3.1.5
#tool nuget:?package=Stratara.Infrastructure&version=3.1.5
Stratara.Infrastructure
License: FSL-1.1-MIT (Functional Source License — source-available; converts to MIT after 2 years). Not OSI-approved OSS.
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). - 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
{
builder.Services.AddSingleton<IKeyStore, AzureKeyVaultKeyStore>(); // or AwsKmsKeyStore, HsmKeyStore, ...
builder.Services.AddSecurity();
}
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)(fromAspNetCore.HealthChecks.Redis) if your host exposes/healthand you want Redis covered. - No automatic OpenTelemetry Redis instrumentation. Add
OpenTelemetry.Instrumentation.StackExchangeRedisand.AddRedisInstrumentation()to yourTracerProviderBuilderif you want Redis spans in your traces.
The connection-string lookup (ConnectionStrings:redis in configuration) is identical to the pre-cleanup behaviour.
| 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
- Azure.Identity (>= 1.21.0)
- Microsoft.AspNetCore.Http.Abstractions (>= 2.3.10)
- Microsoft.Extensions.Configuration.Abstractions (>= 10.0.8)
- Microsoft.Extensions.DependencyInjection (>= 10.0.8)
- Microsoft.Extensions.Logging.Abstractions (>= 10.0.8)
- Microsoft.Extensions.Options.ConfigurationExtensions (>= 10.0.8)
- StackExchange.Redis (>= 2.13.10)
- Stratara.Contracts (>= 3.1.5)
- Stratara.EventSourcing.EntityFrameworkCore (>= 3.1.5)
- Stratara.Mediator (>= 3.1.5)
- Stratara.Outbox.RabbitMQ (>= 3.1.5)
- Stratara.Security (>= 3.1.5)
- Stratara.Sessions (>= 3.1.5)
- Stratara.Shared (>= 3.1.5)
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, AddEventProjectionWorkerServices, AddSagaWorkerServices, AddOutboxWorkerServices) 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.
### Added
- **Configurable snapshot strategy** (`Stratara.Abstractions`, `Stratara.Infrastructure`) — the
snapshot cadence is no longer hard-coded. A new `Stratara.Abstractions.EventSourcing.ISnapshotStrategy`
decides, per stream, whether the event-sourcing runtime should write a snapshot:
`bool ShouldSnapshot(Type aggregateType, long currentVersion, long lastSnapshotVersion)`.
`AddEventSourcing()` registers the default `VersionThresholdSnapshotStrategy` (snapshot every 50
versions — identical to the previous behaviour) via `TryAddSingleton`, so existing consumers see no
change. To take over the policy, register your own singleton `ISnapshotStrategy` (it overrides the
default whether registered before or after `AddEventSourcing()`): vary the threshold per aggregate
type, construct `new VersionThresholdSnapshotStrategy(threshold)` for a different uniform cadence, or
register `NoSnapshotStrategy` to disable snapshotting entirely. This replaces the previously
hard-coded `UseSnapshots`/`SnapshotRange` constants in the default snapshot service, which were not
actually configurable despite the documentation implying they were.
- **`AddDomainEventTypesFromAssemblyContaining<T>()`** (`Stratara.Abstractions`) — registers *only* the
domain event types consumed by an assembly's aggregate `Apply(TEvent)` methods in the trusted-type
resolver, without registering the aggregate types themselves and without pulling any projection / saga
/ command-handler classes into DI. Use it in a host that only needs to deserialize event payloads off
the message bus or event stream — typically a dedicated projection or saga worker — but must not wire
the handler classes (and their runtime dependencies) that `AddProjectionsFromAssemblyContaining<T>`
would register. Complements the existing `AddAggregatesFromAssemblyContaining<T>` (which additionally
registers the aggregate types) and `AddTrustedType<T>` (single type).