Stratara.Domain 4.0.2

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.0.2
                    


                    

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


                            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.0.2
                    


                    

                
#r "nuget: Stratara.Domain, 4.0.2"
#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.0.2
#: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.0.2
                    


                            Install as a Cake Addin
                        

                    

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


                            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 — a read-side event: it carries a customer's deleted tenant ids for TenantProjection and has no Apply() overload on the aggregate. Rehydration skips unmapped events silently, so don't expect it to move aggregate state.

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.0.3 153 9/3/2026
4.0.2 402 9/3/2026
4.0.1 181 9/2/2026
4.0.0 517 8/31/2026
4.0.0-preview.1 102 8/31/2026
3.4.0 296 8/28/2026
3.3.0 452 8/25/2026
3.2.3 272 8/22/2026
3.2.2 832 8/14/2026
3.2.1 852 8/2/2026
3.2.0 257 7/18/2026
3.1.7 486 7/1/2026
3.1.6 676 6/22/2026
3.1.5 255 6/22/2026
3.1.4 265 6/15/2026
3.1.3 264 6/10/2026
3.1.2 274 6/5/2026
3.1.1 327 6/1/2026
3.1.0 242 5/30/2026
3.0.23 233 5/28/2026

Two operational fixes, both found while a consumer rolled out bus-envelope signing and reasoned
about rebuilding its read models: a projection replay now survives a passing failure, and an
integrity failure says whether the signature was absent or wrong. Additive on every published
surface.

### Added

- **A projection replay retries a failing batch before it gives up.** Each batch — the read from
 the event store and the application of its entries — now runs under a new named policy,
 `ResilienceNames.ProjectionReplayBatch`: five attempts in all, exponential backoff from one second
 with jitter between them, any exception except cancellation. A read-store timeout or a
 dropped connection mid-rebuild no longer ends the replay; a failure that persists through every
 attempt ends it exactly as before, with the same failure record. A retried batch is applied
 again from its first entry in a fresh scope, which relies on the guarantee projections already
 give under at-least-once delivery: a second application converges (see *Write handlers that
 converge rather than accumulate* in the projection guide). Each failed attempt logs a new
 warning, `104_011`. `AddResiliencePipelines` registers six policies rather than five. Nothing
 about truncation, ordering, progress, the failure record or the lease changes.

### Changed

- **An integrity failure now says whether the signature was absent or wrong, and the existing
 warning and error ids fire only for a signature that is present and does not verify.** An
 unsigned envelope — what every not-yet-restarted publisher emits during a `Permissive` roll —
 was logged as *"signature mismatch"* under the same id as a key mismatch or tampering, so an
 operator could not tell a rolling restart from an attack without correlating host start times.
 Four new event ids carry the unsigned case: `105_004` (command, permissive), `111_004` (event
 bundle, permissive), `105_105` (command, strict) and `111_105` (event bundle, strict). The
 existing `105_003`, `111_003`, `105_104` and `111_104` keep their numbers and their level but
 now mean a present signature that did not verify; an alert keyed on one of them goes quiet
 during a roll instead of firing for every unsigned message. Strict-mode rejections name the
 case in their exception message. `BusEnvelopeIntegrityVerifier.Verify` gains an overload with
 `out BusEnvelopeIntegrityFailure` (`None`, `Absent`, `Invalid`); the existing overload and the
 `BusEnvelopeIntegrityResult` values are unchanged. An absent signature no longer reaches the
 signer, which already answered `false` for it.