Stratara.Abstractions 3.1.1

dotnet add package Stratara.Abstractions --version 3.1.1
                    
NuGet\Install-Package Stratara.Abstractions -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.Abstractions" Version="3.1.1" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Stratara.Abstractions" Version="3.1.1" />
                    
Directory.Packages.props
<PackageReference Include="Stratara.Abstractions" />
                    
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.Abstractions --version 3.1.1
                    
#r "nuget: Stratara.Abstractions, 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.Abstractions@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.Abstractions&version=3.1.1
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.Abstractions&version=3.1.1
                    
Install as a Cake Tool

Stratara.Abstractions

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

Contract interfaces and wire-level POCO records for the Stratara framework. Library-safe — depends only on Microsoft.Extensions.DependencyInjection.Abstractions, Microsoft.Extensions.Logging.Abstractions, and Stratara.Contracts. No EF Core or message-bus runtime.

Use this when you need to reference Stratara types without pulling in any concrete implementation (Mediator runtime, EF Core, RabbitMQ, etc.). Typical consumers: handler/projection libraries that ship without a host.

Contents

  • Stratara.Abstractions.MediatorIMediator, IRequest, IRequest<T>, ICommand, ICommand<T>, IQuery<T>, ICommandHandler<T>, IQueryHandler<T,R>, IPipelineBehavior<T>, IPipelineBehavior<T,R>, IAggregateScopedCommand.
  • Stratara.Abstractions.EventSourcingIAggregationService, IEventSource, IEventStreamRepository, ISnapshotRepository, IEvent, IEvent<T>, IAggregateCreationEvent, IChangeSetHandler, EventChainAnchor, EventSubject, ConcurrencyException. Plus wire-types: EventStreamEntry, Snapshot.
  • Stratara.Abstractions.PersistenceIUnitOfWork, IWriteUnitOfWork, IReadUnitOfWork, ITransaction, IDbResolver.
  • Stratara.Abstractions.OutboxICommandOutboxDispatcher, IEventBundleOutboxDispatcher, IOutboxRepository. Plus wire-type OutboxEntry.
  • Stratara.Abstractions.MessagingIMessageBus, IMessagingIdentifier, IEventBusConsumer, IEventBusPublisher.
  • Stratara.Abstractions.SessionISessionContextProvider.
  • Stratara.Abstractions.MultitenancyITenantService, ICurrentUserService.
  • Stratara.Abstractions.ProjectionsIProjectionReplayState.
  • Stratara.Abstractions.SecurityIEncryptionFactory, IKeyStore, IMasterKeyProvider, ISecureBlobEncryptor, ISecureJsonSerializer. Plus wire-types: KeyScope, KeyMaterial, EncryptedData, DataSensitivityLevel, EncryptDataAttribute.
  • Stratara.Abstractions.ValidationIValidator<T>, ValidationResult, ValidationFailure, ValidationSeverity, StrataraValidationException.
  • Stratara.Abstractions.EntitiesIEntity, IBucket, IHasRowVersion, IMultiTenant, ITenantEntity, IUserIdentity.
  • Stratara.Abstractions.BackgroundTasksIBackgroundTaskQueue. Plus wire-types: BackgroundTaskInfo, BackgroundTaskStatus.
  • Stratara.Abstractions.CommandsIUpdateCommand.
  • Stratara.Abstractions.AuthorizationRequireRoleAttribute, IAuthorizationProvider, AuthorizationException.

Why split

NuGet consumers without an event-sourcing host can adopt Stratara's CQRS contracts and authorization model without dragging in EF Core, RabbitMQ, or the WriteStore.

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

Showing the top 5 NuGet packages that depend on Stratara.Abstractions:

Package Downloads
Stratara.Sessions

ASP.NET Core middleware and provider for Stratara's Actor/Subject session model. Reads tenant and user from JWT claims (or X-Tenant-Id / X-Client-Id headers) and populates the ambient ISessionContextProvider for every request.

Stratara.Domain

Concrete domain types for the Stratara framework — the Tenant aggregate and its lifecycle events. Stratara's opinionated multitenancy model.

Stratara.Shared

Umbrella package for the Stratara framework — source-generated logger extensions for outbox / saga / projection / messaging, domain-event helpers, merge primitives, and the Tier-A/B abstractions surface re-exported as one transitive bundle.

Stratara.Mediator

In-process mediator with DI-resolved handlers and pipeline behaviors for the Stratara framework. MediatR-style routing via typed wrapper cache, plus an authorizing decorator and a bucket-lock concurrency primitive.

Stratara.Outbox.RabbitMQ

Outbox-pattern command and event dispatch for the Stratara event-sourced stack — RabbitMQ IMessageBus implementation, retry worker, mediator command worker, and Redis-coordinated projection-replay state. Azure Service Bus support ships as the sibling Stratara.Outbox.AzureServiceBus package.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
3.1.1 0 6/1/2026
3.1.0 76 5/30/2026
3.0.23 117 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.