Stratara.Abstractions
4.6.1
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Abstractions --version 4.6.1
NuGet\Install-Package Stratara.Abstractions -Version 4.6.1
<PackageReference Include="Stratara.Abstractions" Version="4.6.1" />
<PackageVersion Include="Stratara.Abstractions" Version="4.6.1" />
<PackageReference Include="Stratara.Abstractions" />
paket add Stratara.Abstractions --version 4.6.1
#r "nuget: Stratara.Abstractions, 4.6.1"
#:package Stratara.Abstractions@4.6.1
#addin nuget:?package=Stratara.Abstractions&version=4.6.1
#tool nuget:?package=Stratara.Abstractions&version=4.6.1
Stratara.Abstractions
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
License: MIT.
Contract interfaces and wire-level POCO records for the Stratara framework. Library-safe — depends only on Microsoft.Extensions.DependencyInjection.Abstractions, Microsoft.Extensions.Logging.Abstractions, and Stratara.Contracts. No EF Core or message-bus runtime.
Use this when you need to reference Stratara types without pulling in any concrete implementation (Mediator runtime, EF Core, RabbitMQ, etc.). Typical consumers: handler/projection libraries that ship without a host.
Contents
Stratara.Abstractions.Mediator—IMediator,IRequest,IRequest<T>,ICommand,ICommand<T>,IQuery<T>,ICommandHandler<T>,IQueryHandler<T,R>,IPipelineBehavior<T>,IPipelineBehavior<T,R>,IAggregateScopedCommand.Stratara.Abstractions.EventSourcing—IAggregationService,IEventSource,IEventStreamRepository,ISnapshotRepository,IEvent,IEvent<T>,IAggregateCreationEvent,IChangeSetHandler,EventChainAnchor,EventSubject,ConcurrencyException. Plus wire-types:EventStreamEntry,Snapshot.Stratara.Abstractions.Persistence—IUnitOfWork,IWriteUnitOfWork,IReadUnitOfWork,ITransaction,IDbResolver.Stratara.Abstractions.Outbox—ICommandOutboxDispatcher,IEventBundleOutboxDispatcher,IOutboxRepository. Plus wire-typeOutboxEntry.Stratara.Abstractions.Messaging—IMessageBus,IMessagingIdentifier,IEventBusConsumer,IEventBusPublisher.Stratara.Abstractions.Session—ISessionContextProvider.Stratara.Abstractions.Multitenancy—ITenantService,ICurrentUserService,ITenantScopedRequest,ICrossTenantAuthorizer,TenantAccessDeniedException,ITenantMembershipStore. Plus wire-types:TenantMembership,MembershipStatus.Stratara.Abstractions.Projections—IProjectionReplayState. Plus wire-types:ReplayProgress,ReplayOutcome,ReplayCompletion,ReplayResult.Stratara.Abstractions.Security—IEncryptionFactory,IKeyStore,IMasterKeyProvider,ISecureBlobEncryptor,ISecureJsonSerializer. Plus wire-types:KeyScope,KeyMaterial,EncryptedData,DataSensitivityLevel,EncryptDataAttribute.Stratara.Abstractions.Validation—IValidator<T>,ValidationResult,ValidationFailure,ValidationSeverity,StrataraValidationException.Stratara.Abstractions.Entities—IEntity,IBucket,IHasRowVersion,IMultiTenant,ITenantEntity,IUserIdentity.Stratara.Abstractions.BackgroundTasks—IBackgroundTaskQueue. Plus wire-types:BackgroundTaskInfo,BackgroundTaskStatus.Stratara.Abstractions.Commands—IUpdateCommand.Stratara.Abstractions.Authorization—RequireRoleAttribute,RequirePermissionAttribute,IAuthorizationProvider,IPermissionResolver,PermissionCatalog,AuthorizationException,PermissionAuthorizationException.Stratara.Abstractions.Settings—ISettingProvider,ISettingStore,SettingCatalog. Plus wire-types:SettingDefinition,SettingScope.Stratara.Abstractions.ApiKeys—IApiKeyStore. Plus wire-types:ApiKeyDescriptor,ApiKeyIssueRequest,IssuedApiKey.
Why split
NuGet consumers without an event-sourcing host can adopt Stratara's CQRS contracts and authorization model without dragging in EF Core, RabbitMQ, or the WriteStore.
| 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
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.13)
- Microsoft.Extensions.Logging.Abstractions (>= 10.0.13)
- Stratara.Contracts (>= 4.6.1)
NuGet packages (14)
Showing the top 5 NuGet packages that depend on Stratara.Abstractions:
| Package | Downloads |
|---|---|
|
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.Domain
Concrete domain types for the Stratara framework — the Tenant aggregate and its lifecycle events. Stratara's opinionated multitenancy model. |
|
|
Stratara.Resilience
Polly-based named resilience pipelines pre-wired for the Stratara framework's messaging and command/event dispatch paths. Four named pipelines registered via AddResiliencePipelines(). |
|
|
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.Mediator
In-process mediator with DI-resolved handlers and pipeline behaviors for the Stratara framework. MediatR-style routing via typed wrapper cache, plus an authorizing decorator and a bucket-lock concurrency primitive. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.8.0 | 461 | 11/6/2026 |
| 4.7.1 | 411 | 11/5/2026 |
| 4.7.0 | 810 | 10/30/2026 |
| 4.6.1 | 331 | 10/29/2026 |
| 4.6.0 | 421 | 10/28/2026 |
| 4.5.0 | 508 | 10/28/2026 |
| 4.4.10 | 438 | 10/26/2026 |
| 4.4.9 | 344 | 10/26/2026 |
| 4.4.8 | 482 | 10/24/2026 |
| 4.4.7 | 348 | 10/23/2026 |
| 4.4.6 | 456 | 10/22/2026 |
| 4.4.5 | 875 | 10/14/2026 |
| 4.4.4 | 592 | 10/10/2026 |
| 4.4.3 | 318 | 10/10/2026 |
| 4.4.2 | 688 | 10/2/2026 |
| 4.4.1 | 638 | 9/29/2026 |
| 4.4.0 | 375 | 9/27/2026 |
| 4.3.1 | 429 | 9/25/2026 |
| 4.3.0 | 608 | 9/23/2026 |
| 4.2.0 | 385 | 9/18/2026 |
A release about two costs of the Orleans execution model that grew with the deployment rather than with the work.
A commit woke every projection and saga reader of each partition it touched, whatever it had committed. Every one of
them read the new entries and wrote its checkpoint, also when it applied nothing, and every reader polled the store on
its own: every single-event command cost a checkpoint write per projection and saga, and an idle silo with many
consumers kept the store busy with hundreds of reads a second. A commit now costs work only for the readers it
concerns, and an idle silo asks the store a few questions per partition and poll interval.
A recorded command whose handler met a concurrency conflict waited for its hand-over to lapse, 30 seconds by default,
before the drain ran it again; on the bus a conflicting message is redelivered at once. It now runs again within
moments.
### Added
- **`ProjectionGrainOptions.IdleCheckpointInterval`** (default 30 seconds) bounds how long a projection's reader may
hold its checkpoint back past entries it applied nothing for. `TimeSpan.Zero` writes the checkpoint after every
batch, as before.
- **`ICommandIntentStore.CountConflictAsync`** counts a conflict and records it without giving the attempt back, and
answers how many conflicts the command has met. The default records through `RecordConflictAsync` and answers
`null`, so an intent store of your own compiles and behaves as before; the framework's store implements it.
### Changed
- **A commit wakes only the readers whose projection or saga applies one of its event types.** This holds for the
wake-up on a silo with a store-reading role and for `AddStrataraStoreWakeUps()`. Woken by every commit as before:
a stateful saga process, which decides from the event itself, and every reader when the commit holds an event type
the silo cannot resolve or whose upcaster refuses an empty payload, or when the host's upcaster pipeline is its own.
A multi-stream commit wakes, in each partition, the readers of the events it wrote there. In a test host with six
projections of which one applied the commit, ten commits cost 59 store reads before and only the applying
projection's reads now, and a commit nobody applies costs no read when it is made. A reader whose partition moved
past it still reads once at its next poll, and then waits again.
- **A projection's reader writes its checkpoint past entries it applied nothing for later**: with the next batch that
applies something, once `IdleCheckpointInterval` has passed, or when it deactivates. It answers waits for its
projection from the position it holds. A reader whose silo dies before the write reads those entries again and
applies nothing for them. A rebuild or a replay discards a position held back. A saga's reader writes its checkpoint
after every batch as before, because a saga added to a running deployment starts where the host's sagas have
written they read.
- **A poll reads the store only when its partition holds something past the reader's position.** Each silo asks the
store for a partition's head at most once per half poll interval, for all its readers. In the test host, 96 idle
readers polling every 500 ms read the store about 960 times in five seconds before and not at all now. A lost
wake-up is applied within about one and a half poll intervals rather than one. A committed position reader that
does not override `ICommittedPositionReader.HeadAsync` keeps polling as before.
- **A conflicting recorded command runs again at once.** The silo that ran it runs it again in a unit of work of its
own while it still holds the hand-over, pausing as the `ResilienceNames.ConcurrencyConflict` pipeline does (five
retries from 50 ms), on the aggregate activation's scheduler. A heavy command keeps its permit. Every conflict is
still recorded and counted, and the command runs again only while its conflicts stay within
`MessageRetryOptions.MaxConflictRequeues`, so a command that conflicts on every attempt runs as often as before and
is kept. The hand-over's attempt is given back once when the command leaves on a conflict, however often it ran.
After the pipeline's retries the drain resumes it as before.
- **`ExecutionModelTestHost.WaitForReadersAsync` waits for the readers' positions**, not their stored checkpoints,
so it returns once every reader has read to the head, whether or not it has written its checkpoint there yet.
**Upgrading:** nothing to do. Hosts and silos of 4.6.0 and of this release mix in a rolling deployment: the cluster
wake-up keeps its form, an earlier host's wake-up wakes every reader, and an earlier silo wakes every reader of a newer
host's wake-up. Checkpoints keep their form. An intent store of your own keeps the old timing after a conflict until
it implements `CountConflictAsync`.