Stratara.Domain
3.0.23
See the version list below for details.
dotnet add package Stratara.Domain --version 3.0.23
NuGet\Install-Package Stratara.Domain -Version 3.0.23
<PackageReference Include="Stratara.Domain" Version="3.0.23" />
<PackageVersion Include="Stratara.Domain" Version="3.0.23" />
<PackageReference Include="Stratara.Domain" />
paket add Stratara.Domain --version 3.0.23
#r "nuget: Stratara.Domain, 3.0.23"
#:package Stratara.Domain@3.0.23
#addin nuget:?package=Stratara.Domain&version=3.0.23
#tool nuget:?package=Stratara.Domain&version=3.0.23
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.0.23)
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.
**First publication to nuget.org.** The complete 20-package Stratara family is now
available on the public [nuget.org](https://www.nuget.org/packages?q=Stratara) feed in
addition to the internal Azure Artifacts feed. External consumers can now run
`dotnet add package Stratara.Mediator` (and the rest of the family) directly. This release
carries the same API and behaviour as 3.0.22 — the only change is public distribution.
### Changed
- **Distribution.** Packages are now pushed to nuget.org on every `v*` tag, gated behind a
manual approval, in addition to the existing internal feed. Symbol packages (`.snupkg`)
are forwarded to symbols.nuget.org automatically.