Stratara.Contracts
4.4.2
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Contracts --version 4.4.2
NuGet\Install-Package Stratara.Contracts -Version 4.4.2
<PackageReference Include="Stratara.Contracts" Version="4.4.2" />
<PackageVersion Include="Stratara.Contracts" Version="4.4.2" />
<PackageReference Include="Stratara.Contracts" />
paket add Stratara.Contracts --version 4.4.2
#r "nuget: Stratara.Contracts, 4.4.2"
#:package Stratara.Contracts@4.4.2
#addin nuget:?package=Stratara.Contracts&version=4.4.2
#tool nuget:?package=Stratara.Contracts&version=4.4.2
Stratara.Contracts
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
License: MIT.
Wire-level POCO contracts shared by every Stratara package. Pure data records — no runtime, no DI, no infrastructure deps. Safe to reference from any layer.
Contents
Messages/EventMessage,EventBundle,CommandEnvelope— the cross-process envelope shapes that messaging adapters (Stratara.Outbox.RabbitMQetc.) serialise on and off the bus.Requests/PagedRequest— shared pagination + sort record used by query handlers across the family.Session/SessionContext— public data shape for actor/subject identity, correlation, causation, and connection routing. TheISessionContextProviderservice abstraction lives inStratara.Abstractions; the ASP.NET Core middleware that populates it lives inStratara.Sessions.
Quick reference
// Build a CommandEnvelope outside the framework (rare, but supported)
var envelope = new CommandEnvelope(
Id: Guid.CreateVersion7(),
CommandJson: commandJson,
CommandTypeName: typeof(MyCommand).AssemblyQualifiedName!,
SessionContextJson: sessionContextJson);
Dependencies
None. Contracts is the lowest tier in the Stratara dependency graph.
| 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
- No dependencies.
NuGet packages (9)
Showing the top 5 NuGet packages that depend on Stratara.Contracts:
| Package | Downloads |
|---|---|
|
Stratara.Abstractions
Contract interfaces and POCO records for the Stratara CQRS / Event Sourcing framework — Mediator, EventSourcing, Persistence, Outbox, Messaging, Session, Security, Authorization. Library-safe, no EF Core or message-bus runtime. |
|
|
Stratara.Sessions
ASP.NET Core middleware and provider for Stratara's Actor/Subject session model. Reads tenant and user from JWT claims (or X-Tenant-Id / X-Client-Id headers) and populates the ambient ISessionContextProvider for every request. |
|
|
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.Outbox.RabbitMQ
Outbox-pattern command and event dispatch for the Stratara event-sourced stack — RabbitMQ IMessageBus implementation, retry worker, mediator command worker, and Redis-coordinated projection-replay state. Azure Service Bus support ships as the sibling Stratara.Outbox.AzureServiceBus package. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.4.3 | 0 | 10/10/2026 |
| 4.4.2 | 547 | 10/2/2026 |
| 4.4.1 | 621 | 9/29/2026 |
| 4.4.0 | 361 | 9/27/2026 |
| 4.3.1 | 415 | 9/25/2026 |
| 4.3.0 | 601 | 9/23/2026 |
| 4.2.0 | 366 | 9/18/2026 |
| 4.1.1 | 371 | 9/16/2026 |
| 4.1.0 | 299 | 9/16/2026 |
| 4.0.4 | 1,167 | 9/14/2026 |
| 4.0.3 | 418 | 9/3/2026 |
| 4.0.2 | 822 | 9/3/2026 |
| 4.0.1 | 500 | 9/2/2026 |
| 4.0.0 | 879 | 8/31/2026 |
| 4.0.0-preview.1 | 166 | 8/31/2026 |
| 3.4.0 | 395 | 8/28/2026 |
| 3.3.0 | 554 | 8/25/2026 |
| 3.2.3 | 380 | 8/22/2026 |
| 3.2.2 | 933 | 8/14/2026 |
| 3.2.1 | 938 | 8/2/2026 |
A release about a flag that cost too much. Every host sharing the replay coordination state over Redis
asked Redis, with a blocking round trip on the calling thread, whether a replay was active — and the
Orleans execution model asked on every hot path, eight to ten times per command on a host with three
projections, inside grain turns. On a two-core host that was enough to starve the thread pool and time
the Redis connection out, surfacing as failed catch-ups, lagging read models and failed grain
registrations although no replay ever ran. The answer now comes from memory. No migration is needed;
one optional setting is new.
### Fixed
- **No path waits on Redis to learn whether a replay is active.** The Redis-backed replay state answers
`IsReplayActive` from a field. A change made in the host itself is seen there at once; a change made
elsewhere — a replay that began or ended in another host, or a marking that lapsed — is announced over
a channel beside the replay-request channel and seen within its latency, and every host re-reads the
marking every `ProjectionReplay:RefreshSeconds` regardless, as the safety net for a lost announcement.
The Orleans execution model's command dispatcher, bundle dispatcher, store readers and drain, and the
bus dispatchers, make no Redis call for it any more. Nothing changes for a host without Redis, whose
state was in process already, nor for a host that registers its own `IProjectionReplayState`.
### Added
- **`ProjectionReplayOptions.RefreshSeconds`** (default 5), read from the `ProjectionReplay` section
like the lease. It bounds how long a host answers from a replay marking that changed elsewhere where the
announcement was lost. Refused when the host starts at zero or below, and at or above
`LeaseSeconds`, with an `OptionsValidationException` naming `ProjectionReplay:RefreshSeconds`.
- **Log events `104_015` to `104_018`.** A host that cannot refresh the replay marking from Redis says
so once at Warning (`104_015`) and keeps its last answer; `104_016` at Information says it reads the
marking again. A host that cannot subscribe to the marking's announcements says so once at Warning
(`104_017`), sees a change on the refresh period only, and `104_018` says it is subscribed again.
### Changed
- **A host that cannot reach Redis keeps its last answer about the replay.** Before, every dispatch and
every catch-up on such a host failed with the connection's exception. Now they proceed on what the host
last learned — initially that no replay is active — and the loss is logged once. The replay stays
correct regardless: on the Orleans execution model the readers are paused by the rebuild and the
replay themselves, and apply the store from the beginning once more when the replay ends.
- **Rolling upgrade.** A host on a release before this one announces nothing when it starts or ends a
replay, so a host on this release sees that replay at the refresh period rather than at once. The
marking, its key and its lease are unchanged, so the two releases share one replay state.