Stratara.Orleans.EntityFrameworkCore
4.4.8
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Orleans.EntityFrameworkCore --version 4.4.8
NuGet\Install-Package Stratara.Orleans.EntityFrameworkCore -Version 4.4.8
<PackageReference Include="Stratara.Orleans.EntityFrameworkCore" Version="4.4.8" />
<PackageVersion Include="Stratara.Orleans.EntityFrameworkCore" Version="4.4.8" />
<PackageReference Include="Stratara.Orleans.EntityFrameworkCore" />
paket add Stratara.Orleans.EntityFrameworkCore --version 4.4.8
#r "nuget: Stratara.Orleans.EntityFrameworkCore, 4.4.8"
#:package Stratara.Orleans.EntityFrameworkCore@4.4.8
#addin nuget:?package=Stratara.Orleans.EntityFrameworkCore&version=4.4.8
#tool nuget:?package=Stratara.Orleans.EntityFrameworkCore&version=4.4.8
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.4.8)
- Stratara.Orleans (>= 4.4.8)
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 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.