Stratara.Orleans.EntityFrameworkCore
4.4.2
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Orleans.EntityFrameworkCore --version 4.4.2
NuGet\Install-Package Stratara.Orleans.EntityFrameworkCore -Version 4.4.2
<PackageReference Include="Stratara.Orleans.EntityFrameworkCore" Version="4.4.2" />
<PackageVersion Include="Stratara.Orleans.EntityFrameworkCore" Version="4.4.2" />
<PackageReference Include="Stratara.Orleans.EntityFrameworkCore" />
paket add Stratara.Orleans.EntityFrameworkCore --version 4.4.2
#r "nuget: Stratara.Orleans.EntityFrameworkCore, 4.4.2"
#:package Stratara.Orleans.EntityFrameworkCore@4.4.2
#addin nuget:?package=Stratara.Orleans.EntityFrameworkCore&version=4.4.2
#tool nuget:?package=Stratara.Orleans.EntityFrameworkCore&version=4.4.2
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.2)
- Stratara.Orleans (>= 4.4.2)
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.
A release about a flag that cost too much. Every host sharing the replay coordination state over Redis
asked Redis, with a blocking round trip on the calling thread, whether a replay was active — and the
Orleans execution model asked on every hot path, eight to ten times per command on a host with three
projections, inside grain turns. On a two-core host that was enough to starve the thread pool and time
the Redis connection out, surfacing as failed catch-ups, lagging read models and failed grain
registrations although no replay ever ran. The answer now comes from memory. No migration is needed;
one optional setting is new.
### Fixed
- **No path waits on Redis to learn whether a replay is active.** The Redis-backed replay state answers
`IsReplayActive` from a field. A change made in the host itself is seen there at once; a change made
elsewhere — a replay that began or ended in another host, or a marking that lapsed — is announced over
a channel beside the replay-request channel and seen within its latency, and every host re-reads the
marking every `ProjectionReplay:RefreshSeconds` regardless, as the safety net for a lost announcement.
The Orleans execution model's command dispatcher, bundle dispatcher, store readers and drain, and the
bus dispatchers, make no Redis call for it any more. Nothing changes for a host without Redis, whose
state was in process already, nor for a host that registers its own `IProjectionReplayState`.
### Added
- **`ProjectionReplayOptions.RefreshSeconds`** (default 5), read from the `ProjectionReplay` section
like the lease. It bounds how long a host answers from a replay marking that changed elsewhere where the
announcement was lost. Refused when the host starts at zero or below, and at or above
`LeaseSeconds`, with an `OptionsValidationException` naming `ProjectionReplay:RefreshSeconds`.
- **Log events `104_015` to `104_018`.** A host that cannot refresh the replay marking from Redis says
so once at Warning (`104_015`) and keeps its last answer; `104_016` at Information says it reads the
marking again. A host that cannot subscribe to the marking's announcements says so once at Warning
(`104_017`), sees a change on the refresh period only, and `104_018` says it is subscribed again.
### Changed
- **A host that cannot reach Redis keeps its last answer about the replay.** Before, every dispatch and
every catch-up on such a host failed with the connection's exception. Now they proceed on what the host
last learned — initially that no replay is active — and the loss is logged once. The replay stays
correct regardless: on the Orleans execution model the readers are paused by the rebuild and the
replay themselves, and apply the store from the beginning once more when the replay ends.
- **Rolling upgrade.** A host on a release before this one announces nothing when it starts or ends a
replay, so a host on this release sees that replay at the refresh period rather than at once. The
marking, its key and its lease are unchanged, so the two releases share one replay state.