Stratara.Orleans.EntityFrameworkCore
4.7.1
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Orleans.EntityFrameworkCore --version 4.7.1
NuGet\Install-Package Stratara.Orleans.EntityFrameworkCore -Version 4.7.1
<PackageReference Include="Stratara.Orleans.EntityFrameworkCore" Version="4.7.1" />
<PackageVersion Include="Stratara.Orleans.EntityFrameworkCore" Version="4.7.1" />
<PackageReference Include="Stratara.Orleans.EntityFrameworkCore" />
paket add Stratara.Orleans.EntityFrameworkCore --version 4.7.1
#r "nuget: Stratara.Orleans.EntityFrameworkCore, 4.7.1"
#:package Stratara.Orleans.EntityFrameworkCore@4.7.1
#addin nuget:?package=Stratara.Orleans.EntityFrameworkCore&version=4.7.1
#tool nuget:?package=Stratara.Orleans.EntityFrameworkCore&version=4.7.1
Stratara.Orleans.EntityFrameworkCore
Derived. The behaviour described here is specified under
openspec/specs/, in theorleans-executionandevent-sourcing-storecapabilities. 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 | 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
- Stratara.EventSourcing.EntityFrameworkCore (>= 4.7.1)
- Stratara.Orleans (>= 4.7.1)
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 |
A patch for the shared identity store: single roles of a membership can now change without losing a concurrent
change, and a fresh store's first migration no longer logs a spurious error.
### Added
- **`ITenantMembershipStore.AddRolesAsync` and `RemoveRolesAsync`** give or take single roles of one membership,
leaving its other roles and its status as they are, and return the membership afterwards (`null` where there is
none — neither creates one). On the framework's stores two overlapping role changes to the same membership both
take effect; a store that keeps losing to concurrent writers throws `InvalidOperationException` instead of dropping
the change. No schema change. Both are default interface methods, so a store you implemented yourself keeps
compiling and gets them as a read followed by a whole write — without protection against a concurrent writer.
`TenantMembership.WithRolesAdded` and `WithRolesRemoved` compute the changed role set.
### Fixed
- **`MigrateStrataraIdentityStoreAsync()` no longer logs an `Error` on a fresh database.** The first migration of an
empty identity store logged a failed read of its migration history table from
`Microsoft.EntityFrameworkCore.Database.Command`, although the migration then succeeded. The database, the schema and
the history table are now created before the migrations run, so a first start logs nothing at `Error` or above —
also when several hosts start against an empty store at once.