Stratara.Domain
3.2.2
dotnet add package Stratara.Domain --version 3.2.2
NuGet\Install-Package Stratara.Domain -Version 3.2.2
<PackageReference Include="Stratara.Domain" Version="3.2.2" />
<PackageVersion Include="Stratara.Domain" Version="3.2.2" />
<PackageReference Include="Stratara.Domain" />
paket add Stratara.Domain --version 3.2.2
#r "nuget: Stratara.Domain, 3.2.2"
#:package Stratara.Domain@3.2.2
#addin nuget:?package=Stratara.Domain&version=3.2.2
#tool nuget:?package=Stratara.Domain&version=3.2.2
Stratara.Domain
License: MIT.
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— the event records consumed by the aggregate'sApply()methods + persisted to the event stream.Stratara.Domain.CustomerTenantsDeleted— a read-side event: it carries a customer's deleted tenant ids forTenantProjectionand has noApply()overload on the aggregate. Rehydration skips unmapped events silently, so don't expect it to move aggregate state.
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.2.2)
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 command flows, 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.
API keys can now be bootstrapped. Issuance always generated the key itself, which does not fit the
setups where server and caller have to share a key *before* either starts — container orchestration,
CI provisioning, self-hosted bundles, end-to-end test hosts. This release adds an import path for a
key the caller already holds, plus the canonical key format as public API so callers generate values
instead of inventing them.
### Added
- **`IApiKeyStore.ImportAsync` — store a machine key whose raw value the caller already holds.**
Issuance generates the key itself, which is the wrong shape when server and caller must share it
*before* either boots: container orchestration, CI provisioning, self-hosted bundles, end-to-end
test hosts. Without this path, consumers bypassed the store and reimplemented its internals (the
digest format and the machine-key membership row) — a copy that keeps compiling after the store
changes and fails as a runtime 401. Import is idempotent, so it can run unconditionally on every
boot: a value that is already stored returns the existing descriptor and the stored key is never
mutated, so a changed configuration cannot escalate a key's roles or extend its expiry unnoticed.
Revoked, expired, and foreign-tenant values are rejected rather than silently adopted, and
concurrent replicas racing the same first import converge on one key. Machine keys only —
`ApiKeyImportRequest` carries no `UserId`.
- **`ApiKeyFormat` (`Stratara.Abstractions.ApiKeys`) — the canonical raw-key format as public API.**
`CreateRawKey()` generates `stk_` plus the Base64Url encoding of 32 CSPRNG bytes; `IsWellFormed()`
checks that shape. `ImportAsync` accepts only well-formed values: the store keeps its stored
digest unsalted because a generated key carries 256 bits of entropy, and a hand-picked value would
quietly invalidate that. Generate keys out of band with `CreateRawKey()` and keep them in a secret
store — the type lives in the abstractions package so host-builder and orchestration projects can
reach it without referencing the storage implementation.
- **`InMemoryApiKeyStore` (`Stratara.Testing`) — the drop-in double for the API-key store**,
mirroring issuance, import, fail-closed validation, revocation, and the erasure sweeps, and
materializing machine keys into a membership store you can share and inspect.
### Changed
- **API-key lifecycle events are now logged** (`Stratara.Diagnostics` event-ID range 116_000):
import, idempotent repeat, and a repeat that supplied different parameters. Key ids and tenant
ids only — never the raw key or its digest.
- **For implementers of `IApiKeyStore`:** the interface gained `ImportAsync`. Custom implementations
need the new member; callers are unaffected.