Stratara.Domain 4.4.10

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package Stratara.Domain --version 4.4.10
                    
NuGet\Install-Package Stratara.Domain -Version 4.4.10
                    
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.4.10" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Stratara.Domain" Version="4.4.10" />
                    
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.4.10
                    
#r "nuget: Stratara.Domain, 4.4.10"
                    
#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.4.10
                    
#: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.4.10
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.Domain&version=4.4.10
                    
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 261 11/6/2026
4.7.1 268 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 410 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 526 10/10/2026
4.4.3 281 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 363 9/25/2026
4.3.0 546 9/23/2026
4.2.0 321 9/18/2026
Loading failed

A release for hosts on the Orleans execution model. A durable timer now answers its tick while its handler runs, so a
long handler leaves no reminder error in the silo's log, and a timer that fails is logged by the framework with its
owner and purpose. A commit no longer constructs every registered projection to learn which store readers to wake. No
API change, no schema change and no migration.

### Changed

- **A commit no longer constructs every projection.** On the Orleans execution model, every command that committed
 facts constructed each registered projection, with its dependencies, only to learn the names of the store readers to
 wake. The names are now worked out once per silo, and the wait for a projection, the rebuild and the full replay's
 checkpoint reset use the same list. A rebuild of a name that is not registered is refused before any reader is
 paused, with the same message as before.

### Fixed

- **A durable timer answers its tick while its handler runs.** On the Orleans execution model, a durable timer's
 reminder call stayed open until its handler returned, so a handler longer than the runtime's response timeout made
 Orleans log `Could not deliver reminder tick` at Error for every tick it outlasted. The tick is now answered at once
 and the handler runs in a call that carries no response timeout. The timer still fires once per due time, a tick
 during its handler still does nothing, and a handler stopped with its silo still fires again on the next one.
- **A failing timer is logged.** A durable timer whose handler threw — or whose owner check or unregistration
 failed — was visible only as Orleans' reminder error line. It is now logged as `117_137` `TimerFiringFailed` (Error)
 with the owner, the purpose and the exception, and the timer fires again after its retry period as before.