Stratara.Domain 4.6.0

Prefix Reserved
.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package Stratara.Domain --version 4.6.0
                    


                    

                
NuGet\Install-Package Stratara.Domain -Version 4.6.0
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.Domain" Version="4.6.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Stratara.Domain" Version="4.6.0" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Stratara.Domain" />
                    


                            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.Domain --version 4.6.0
                    


                    

                
#r "nuget: Stratara.Domain, 4.6.0"
#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.Domain@4.6.0
#: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.Domain&version=4.6.0
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Stratara.Domain&version=4.6.0
                    


                            Install as a Cake Tool

Stratara.Domain

Derived. The behaviour described here is specified under openspec/specs/. Those specifications are the source; this page explains and illustrates them.

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. Implements IAggregate (from Stratara.Abstractions).
  • Stratara.Domain.TenantCreated / TenantRenamed / TenantActivated / TenantDeactivated / TenantDefaultLocaleChanged / TenantAssignedToCustomer / TenantDeleted — the event records consumed by the aggregate's Apply() methods + persisted to the event stream.
  • Stratara.Domain.CustomerTenantsDeleted — the cascade event that deletes all of a customer's tenants at once. You append it to your own customer aggregate's stream; TenantProjection removes the listed tenants from the read model. No framework aggregate applies it, and your customer aggregate needs no Apply() for it: a rebuild skips an event the aggregate has no Apply() for without reading it. In a host that never registers the type, the first skip per process logs a warning; register it there with AddTrustedType<CustomerTenantsDeleted>() to acknowledge it. (An aggregate with an Apply() taking an interface, an abstract class or object reads every unresolvable event instead — see the snapshot guide.) It does not touch the tenants' own streams, so a Tenant rehydrated afterwards reads as deleted only if TenantDeleted was appended to its stream as well.

TenantCreated implements IAggregateCreationEvent, declaring the tenant it creates as the event's own data owner. A tenant therefore belongs to itself no matter which session performed the creation — an operator creating a tenant does not end up owning it. The interface is a compile-time contract read when the event is appended; it is not serialized, so the record's JSON is unchanged.

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 — for IAggregate (Tenant implements it).
  • JetBrains.Annotations — for static-analysis attributes.
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 (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.

Version Downloads Last Updated
4.8.0 203 11/6/2026
4.7.1 206 11/5/2026
4.7.0 729 10/30/2026
4.6.1 265 10/29/2026
4.6.0 341 10/28/2026
4.5.0 425 10/28/2026
4.4.10 359 10/26/2026
4.4.9 267 10/26/2026
4.4.8 408 10/24/2026
4.4.7 284 10/23/2026
4.4.6 385 10/22/2026
4.4.5 808 10/14/2026
4.4.4 524 10/10/2026
4.4.3 280 10/10/2026
4.4.2 631 10/2/2026
4.4.1 574 9/29/2026
4.4.0 302 9/27/2026
4.3.1 361 9/25/2026
4.3.0 546 9/23/2026
4.2.0 321 9/18/2026
Loading failed

An erasure shreds every key that names the subject, and nothing stopped the next encryption for that subject
from creating a new one: a key store asked for a scope it does not hold creates a first version. A job, a request
in flight or a second process that encrypted for an erased subject afterwards got a fresh key, and what it wrote
stayed readable for good. The key store now records an erased subject and refuses to create a key for it again.

### Added

- **`IKeyStore.MarkSubjectErasedAsync(KeySubject)`** records that a tenant or user has been erased. It has a
 default implementation that throws `NotSupportedException`, so an existing key store still compiles.
- **`KeySubject`** names the tenant or user, and `KeySubject.Covers(KeyScope)` states which keys belong to its
 erasure: for a tenant, a key of any level that names it; for a user, a user-level key that names it.
- **`KeyScopeErasedException`** (an `InvalidOperationException`) is what a key store throws for such a scope. It
 carries the refused `Scope`.

### Changed

- **An encryption for an erased subject fails.** After a subject's erasure, `GetOrCreateCurrentKeyAsync` and
 `RotateAsync` throw `KeyScopeErasedException` for every scope the subject covers, whether or not it ever held a
 key, and create nothing. The blob encryptor, the encrypting settings store and the field-encrypting serializer
 pass it through. Code that erased a subject and then wrote encrypted data for it again now sees the exception;
 the mark is permanent and cannot be lifted. Revoking every version of a scope is not an erasure and marks nothing.
- **`ISubjectEraser` marks the subject before it sweeps any plane**, so an encryption racing the erasure
 either creates its key first, and that key is shredded with the rest, or is refused. A key store that cannot mark
 a subject leaves the erasure as before and logs `SubjectNotMarkable` (112009).
- **The file-backed key store writes format version 2**, which holds the marks, and refuses to open a file in a
 newer format than it knows. `InMemoryKeyStore` refuses an erased subject as the file store does; `DummyKeyStore`
 refuses to mark one, as it refuses every erasure operation.

**Upgrading:**
- **Upgrade every process that shares a key store file in one step.** A process on an earlier release reads a
 version-2 file, ignores the marks, creates keys for an erased subject and drops the marks the next time it writes
 the file. A version-1 file needs no migration. Rolling back is possible but loses the marks on the first write.
- **Map `KeyScopeErasedException` to your answer for data that is gone**, if a request can reach an encryption for
 a subject after its erasure.
- **A key store of your own implements `MarkSubjectErasedAsync`**, refusing in `GetOrCreateCurrentKeyAsync` and
 `RotateAsync` every scope a marked subject `Covers`. Without it the erasure warns and the gap stays open.