Stratara.Domain
3.1.1
See the version list below for details.
dotnet add package Stratara.Domain --version 3.1.1
NuGet\Install-Package Stratara.Domain -Version 3.1.1
<PackageReference Include="Stratara.Domain" Version="3.1.1" />
<PackageVersion Include="Stratara.Domain" Version="3.1.1" />
<PackageReference Include="Stratara.Domain" />
paket add Stratara.Domain --version 3.1.1
#r "nuget: Stratara.Domain, 3.1.1"
#:package Stratara.Domain@3.1.1
#addin nuget:?package=Stratara.Domain&version=3.1.1
#tool nuget:?package=Stratara.Domain&version=3.1.1
Stratara.Domain
License: FSL-1.1-MIT (Functional Source License — source-available; converts to MIT after 2 years). Not OSI-approved OSS.
The Stratara framework's concrete multitenancy domain — the Tenant aggregate and its event vocabulary. Use this when your application wants Stratara's opinionated tenant model (one tenant per customer, lifecycle events for activate / deactivate / rename / locale-change / assignment) and the corresponding aggregate.
Contents
Stratara.Domain.Multitenancy.Tenant— the aggregate. ImplementsIAggregate(fromStratara.Abstractions).Stratara.Domain.TenantCreated/TenantRenamed/TenantActivated/TenantDeactivated/TenantDefaultLocaleChanged/TenantAssignedToCustomer/TenantDeleted/CustomerTenantsDeleted— the event records consumed by the aggregate'sApply()methods + persisted to the event stream.
When to skip this package
If you're building a Stratara-on-Mediator application without the framework's tenant model (e.g. you have your own tenancy concept), reference Stratara.Abstractions alone for the marker interfaces. Most Stratara features (CQRS, event sourcing, projections, sagas) don't depend on Stratara.Domain.
Quick reference
// Open a Tenant stream from a command handler
await events.CreateAsync<Tenant>(tenantId,
new TenantCreated(
Id: tenantId,
CustomerId: customerId,
Name: "Acme",
DefaultLocale: "de-DE",
IsActive: true,
CreatedAt: DateTimeOffset.UtcNow),
cancellationToken);
await events.SaveChangesAsync(cancellationToken);
// Later: rehydrate the aggregate
var tenant = await aggregator.AggregateAsync<Tenant>(tenantId, cancellationToken: cancellationToken);
Dependencies
Stratara.Abstractions— forIAggregate(Tenant implements it).JetBrains.Annotations— for static-analysis attributes.
| 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
- JetBrains.Annotations (>= 2025.2.4)
- Stratara.Abstractions (>= 3.1.1)
NuGet packages (3)
Showing the top 3 NuGet packages that depend on Stratara.Domain:
| Package | Downloads |
|---|---|
|
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.Projections
Projection runtime for the Stratara event-sourced stack — projection-handler discovery, change-set creation, update application, and projection manager. Sits between read-model repositories and the event-bundle dispatcher. |
|
|
Stratara.Sagas
Saga runtime for the Stratara event-sourced stack — ISaga discovery, manager / handler dispatch, cached method invoker, and a hosted SagaWorker that routes incoming event bundles to matching sagas. |
GitHub repositories
This package is not used by any popular GitHub repositories.
### 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.