Stratara.Orleans.EntityFrameworkCore 4.6.0

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

Stratara.Orleans.EntityFrameworkCore

Derived. The behaviour described here is specified under openspec/specs/, in the orleans-execution and event-sourcing-store capabilities. Those specifications are the source; this page explains them.

License: MIT.

Entity Framework Core persistence for the Stratara Orleans execution model: the readers that return the event store in commit order and the checkpoint store the store-reading projections and sagas resume from. The columns and tables they need are declared by the framework's write and read contexts in Stratara.EventSourcing.EntityFrameworkCore, so a context derived from those carries them without further configuration.

What's in the box

Part What it does
PostgresTransactionIdReader<TContext> Reads in commit order on PostgreSQL, adding no work to an append
PortableCounterReader<TContext>, AddStrataraPortableCounterReader<TWriteContext>() Reads in commit order on any relational provider, through a per-partition counter; verified on PostgreSQL and on SQLite
PartitionCounterInterceptor Maintains the per-partition counter inside the appending transaction — in every process that appends
PartitionCounterBackfill Positions unpositioned entries after the partition's counter, never moving a position already handed out, so checkpoints stay true
CommitTransactionIdBackfill Stamps the entries a PostgreSQL store held before the commit record existed, in append order and bounded batches, once
AddStrataraProjectionCheckpoints<TReadContext>() Keeps the checkpoints in the read context
AddStrataraIntentStore<TWriteContext>() Records the commands the execution model's dispatcher accepts, in the outbox table, and claims a due batch in two statements
AddStrataraExecutionModelReset<TReadContext>() Clears reminders, membership, directory and the host's checkpoints while no silo runs

Quick start

The read side — projections that read the store in commit order from a checkpoint:

builder.Services
    .AddSingleton<ICommittedPositionReader, PostgresTransactionIdReader<AppWriteDbContext>>()
    .AddStrataraProjectionCheckpoints<AppReadDbContext>()
    .AddStrataraProjectionGrains();

The write side — commands recorded before the dispatch returns and resumed after a crash:

builder.Services
    .AddStrataraOrleansCommandDispatcher()
    .AddStrataraIntentStore<AppWriteDbContext>()
    .AddStrataraSingletonWork<OutboxDrainWork>(OutboxDrainWork.WorkName);

The record is committed in a transaction of its own, not with what the caller writes.

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 (1)

Showing the top 1 NuGet packages that depend on Stratara.Orleans.EntityFrameworkCore:

Package Downloads
Stratara.Testing.Orleans

Run the Stratara Orleans execution model in a test's own process — one silo with in-memory reminders and grain directory, the real write stack, commit-order reader and checkpoint store on in-memory SQLite, and every period shortened to seconds. Register handlers, projections, sagas and timers with the production calls; no cluster, broker or database server. Builds on Stratara.Testing.EntityFrameworkCore.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
4.8.0 152 11/6/2026
4.7.1 134 11/5/2026
4.7.0 444 10/30/2026
4.6.1 116 10/29/2026
4.6.0 178 10/28/2026
4.5.0 269 10/28/2026
4.4.10 216 10/26/2026
4.4.9 124 10/26/2026
4.4.8 261 10/24/2026
4.4.7 124 10/23/2026
4.4.6 219 10/22/2026
4.4.5 107 10/14/2026
4.4.4 111 10/10/2026
4.4.3 116 10/10/2026
4.4.2 243 10/2/2026
4.4.1 130 9/29/2026
4.4.0 106 9/27/2026
4.3.1 118 9/25/2026
4.3.0 155 9/23/2026
4.2.0 178 9/18/2026
Loading failed

An erasure shreds every key that names the subject, and nothing stopped the next encryption for that subject
from creating a new one: a key store asked for a scope it does not hold creates a first version. A job, a request
in flight or a second process that encrypted for an erased subject afterwards got a fresh key, and what it wrote
stayed readable for good. The key store now records an erased subject and refuses to create a key for it again.

### Added

- **`IKeyStore.MarkSubjectErasedAsync(KeySubject)`** records that a tenant or user has been erased. It has a
 default implementation that throws `NotSupportedException`, so an existing key store still compiles.
- **`KeySubject`** names the tenant or user, and `KeySubject.Covers(KeyScope)` states which keys belong to its
 erasure: for a tenant, a key of any level that names it; for a user, a user-level key that names it.
- **`KeyScopeErasedException`** (an `InvalidOperationException`) is what a key store throws for such a scope. It
 carries the refused `Scope`.

### Changed

- **An encryption for an erased subject fails.** After a subject's erasure, `GetOrCreateCurrentKeyAsync` and
 `RotateAsync` throw `KeyScopeErasedException` for every scope the subject covers, whether or not it ever held a
 key, and create nothing. The blob encryptor, the encrypting settings store and the field-encrypting serializer
 pass it through. Code that erased a subject and then wrote encrypted data for it again now sees the exception;
 the mark is permanent and cannot be lifted. Revoking every version of a scope is not an erasure and marks nothing.
- **`ISubjectEraser` marks the subject before it sweeps any plane**, so an encryption racing the erasure
 either creates its key first, and that key is shredded with the rest, or is refused. A key store that cannot mark
 a subject leaves the erasure as before and logs `SubjectNotMarkable` (112009).
- **The file-backed key store writes format version 2**, which holds the marks, and refuses to open a file in a
 newer format than it knows. `InMemoryKeyStore` refuses an erased subject as the file store does; `DummyKeyStore`
 refuses to mark one, as it refuses every erasure operation.

**Upgrading:**
- **Upgrade every process that shares a key store file in one step.** A process on an earlier release reads a
 version-2 file, ignores the marks, creates keys for an erased subject and drops the marks the next time it writes
 the file. A version-1 file needs no migration. Rolling back is possible but loses the marks on the first write.
- **Map `KeyScopeErasedException` to your answer for data that is gone**, if a request can reach an encryption for
 a subject after its erasure.
- **A key store of your own implements `MarkSubjectErasedAsync`**, refusing in `GetOrCreateCurrentKeyAsync` and
 `RotateAsync` every scope a marked subject `Covers`. Without it the erasure warns and the gap stays open.