Stratara.Abstractions 4.4.8

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package Stratara.Abstractions --version 4.4.8
                    
NuGet\Install-Package Stratara.Abstractions -Version 4.4.8
                    
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.Abstractions" Version="4.4.8" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Stratara.Abstractions" Version="4.4.8" />
                    
Directory.Packages.props
<PackageReference Include="Stratara.Abstractions" />
                    
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.Abstractions --version 4.4.8
                    
#r "nuget: Stratara.Abstractions, 4.4.8"
                    
#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.Abstractions@4.4.8
                    
#: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.Abstractions&version=4.4.8
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.Abstractions&version=4.4.8
                    
Install as a Cake Tool

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-type OutboxEntry.
  • 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 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 (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 266 11/6/2026
4.7.1 296 11/5/2026
4.7.0 806 10/30/2026
4.6.1 329 10/29/2026
4.6.0 419 10/28/2026
4.5.0 507 10/28/2026
4.4.10 435 10/26/2026
4.4.9 338 10/26/2026
4.4.8 481 10/24/2026
4.4.7 345 10/23/2026
4.4.6 455 10/22/2026
4.4.5 873 10/14/2026
4.4.4 591 10/10/2026
4.4.3 316 10/10/2026
4.4.2 686 10/2/2026
4.4.1 634 9/29/2026
4.4.0 372 9/27/2026
4.3.1 428 9/25/2026
4.3.0 607 9/23/2026
4.2.0 384 9/18/2026
Loading failed

A fix for hosts on the Orleans execution model. A store reader that catches up a large backlog and a singleton
work that runs long now answer their keep-alive, so neither leaves reminder errors in the silo's log. A silo that
joins while a singleton work runs long on another silo no longer fails its start. No API change, no schema change
and no migration.

### Fixed

- **A busy store reader or singleton work answers its keep-alive.** On the Orleans execution model, a projection or
 saga reader that caught up a backlog for longer than the runtime's response timeout made its keep-alive tick wait
 behind the catch-up, and Orleans logged `Could not deliver reminder tick` at Error, once per partition and
 keep-alive period. A singleton work whose run outlasted the timeout did the same. Nothing was lost, but a large
 catch-up left dozens of errors on the silo. The keep-alive and the poll now start a catch-up where none is
 running and do not wait for it. A partition is still read by one catch-up at a time, and a commit during a
 catch-up is still applied by it. A singleton work's keep-alive interleaves with its run, and runs still never
 overlap.
- **A silo starts while a singleton work runs long.** A silo that started while a singleton work it registers ran
 longer than the response timeout on another silo waited for that run in its own start. The start then failed
 with a `TimeoutException`. The call a starting silo makes to each singleton work and store reader now
 interleaves, so the start goes on.
- *Operate the Orleans execution model* says that a durable timer whose handler outlasts the response timeout
 still makes Orleans log `Could not deliver reminder tick` for that tick, and that the line says nothing about
 the timer. It also says that, outside a deploy, the line now points to an unreachable store reader or singleton
 work rather than a busy one.