Stratara.Orleans.EntityFrameworkCore
4.4.1
Prefix Reserved
dotnet add package Stratara.Orleans.EntityFrameworkCore --version 4.4.1
NuGet\Install-Package Stratara.Orleans.EntityFrameworkCore -Version 4.4.1
<PackageReference Include="Stratara.Orleans.EntityFrameworkCore" Version="4.4.1" />
<PackageVersion Include="Stratara.Orleans.EntityFrameworkCore" Version="4.4.1" />
<PackageReference Include="Stratara.Orleans.EntityFrameworkCore" />
paket add Stratara.Orleans.EntityFrameworkCore --version 4.4.1
#r "nuget: Stratara.Orleans.EntityFrameworkCore, 4.4.1"
#:package Stratara.Orleans.EntityFrameworkCore@4.4.1
#addin nuget:?package=Stratara.Orleans.EntityFrameworkCore&version=4.4.1
#tool nuget:?package=Stratara.Orleans.EntityFrameworkCore&version=4.4.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.4.1)
- Stratara.Orleans (>= 4.4.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.
A release about errors that were not errors. Where two writers insert the same row at once — two
deliveries forgetting a deleted tenant, two activations writing a partition's first checkpoint, two
hosts importing one API key — the framework already recovered, but EF Core had logged the losing
statement at Error first; on PostgreSQL and SQLite the insert now skips a row that is already there.
And a RabbitMQ bus whose broker went away first no longer reports a warning for every subscription it
stops, nor a failed handler for a message it merely could not acknowledge. No migration and no
configuration change is needed.
### Fixed
- **Forgetting a deleted tenant leaves no error in the log when two deliveries race.** A tenant's two
deletion facts arrive in two bundles, so two deliveries of one projection can record the same tenant
at once. The losing insert was caught and the tenant recorded all the same, but EF Core had already
logged the failed statement at Error (`20102` and `10000`), so a customer deletion could leave two
errors in a projection worker's log. On PostgreSQL and SQLite the tenants are now recorded with an
insert that skips a row already there; on other providers the store still retries, and EF Core still
logs the statement that lost.
- **A projection checkpoint's first write, and an API key two hosts import at once, leave no error in
the log.** Two activations of one reader that overlap during a failover can both write a partition's
first checkpoint, and hosts that seed the same key as they boot import it at once. The writer whose
insert lost recovered — it took the other's checkpoint over, or adopted the other's key — but EF Core
had already logged the failed statement at Error. On PostgreSQL and SQLite the insert now skips a row
that is already there, as the record of forgotten tenants does; a checkpoint that another writer
inserted and removed again before it could be taken over is refused with an
`InvalidOperationException`. An import takes that path only where it is the only write on its
context, and then writes the key and its membership in one transaction of its own, outside
`SaveChanges` and its interceptors. An import on a context with unsaved changes or inside a
transaction of the caller's saves through `SaveChanges` as before, and so does a table a consumer
widened with columns the row does not carry, and every other provider: there the writer still
recovers, and EF Core still logs the statement that lost.
- **A RabbitMQ subscription whose broker is already gone stops without a warning.** When a stack stops
its broker before its hosts, a stopping subscription's cancel met a connection that had already
closed, or that closed while the cancel waited for its reply, and every subscription of every host
logged `108_107` at Warning — new in 4.4.0, which made a subscription cancel its consumer before it
closes. A closed connection has no consumer left to cancel, which is where the stop was going, so
this is now logged at Debug as `108_007` (`LogEvents.Messaging.SubscriptionAlreadyClosed`). A cancel
that fails while the connection is still up still warns.
- **A handler that completes after the broker went away is no longer reported as failed.** Its
acknowledgement met a closed channel, and the RabbitMQ bus logged `108_101` at Error although the
handler had succeeded, then tried to reject the message on the same closed channel. It now logs
`108_008` (`LogEvents.Messaging.MessageNotSettledChannelClosed`) at Information: the message could
not be settled, and the broker delivers it again.