RevenueFlow.Events 0.1.0-alpha.7.2

This is a prerelease version of RevenueFlow.Events.
dotnet add package RevenueFlow.Events --version 0.1.0-alpha.7.2
                    
NuGet\Install-Package RevenueFlow.Events -Version 0.1.0-alpha.7.2
                    
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="RevenueFlow.Events" Version="0.1.0-alpha.7.2" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="RevenueFlow.Events" Version="0.1.0-alpha.7.2" />
                    
Directory.Packages.props
<PackageReference Include="RevenueFlow.Events" />
                    
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 RevenueFlow.Events --version 0.1.0-alpha.7.2
                    
#r "nuget: RevenueFlow.Events, 0.1.0-alpha.7.2"
                    
#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 RevenueFlow.Events@0.1.0-alpha.7.2
                    
#: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=RevenueFlow.Events&version=0.1.0-alpha.7.2&prerelease
                    
Install as a Cake Addin
#tool nuget:?package=RevenueFlow.Events&version=0.1.0-alpha.7.2&prerelease
                    
Install as a Cake Tool

History and recoverable dispatch

RevenueEventHistory reads bounded fully scoped live pages. RevenueEventDispatcher polls one consumer at a time, uses atomic revision-checked claims and lease IDs, invokes callbacks after commit and fences stale completion. Failures retry up to the selected attempt budget, then become dead letters. Requested cancellation leaves a lease for conservative recovery.

A crash after handler effects and before completion can redeliver the same event. Consumers must atomically deduplicate their own work using scope/consumer/event identity. Database rollback cannot undo handler effects.

Dispatch scans bounded pages (maximum 100) in UUID order. Durable per-item delivery state survives restarts; the scan cursor is only a performance hint. The optional hosted worker drains useful pages immediately and interleaves finite revisit sweeps, discovering inserts/retries behind a continuously advancing cursor. Stores may implement IRevenueOutboxQueryStore to exclude recognized terminal records, future pending records and unexpired leases before pagination. Generic custom stores retain the complete-scan fallback. Malformed, ownership-mismatched, noncanonical and stale-projection records remain discoverable; the dispatcher validates them again and CAS arbitrates claims. Native indexes/backfill are store responsibilities, and Guid-ordered eligible queries may still scan/sort many due rows. A delivery retains two durable fenced transitions: claim before its handler, completion after its handler. Batching those transitions across unrelated handlers would change lease timing and recovery behavior.

Unreadable history causes that delivery to dead-letter. Unreadable/future outbox content is preserved and counted as Unreadable while healthy records continue. No raw payloads or exception details are logged. Management supports explicit replay of an expected terminal delivery after validating retained schemas. The shared IRevenueEventReader supports bounded deterministic Data upcasters, safe scoped quarantine inspection and audited explicit revalidation. Optional raw-only content deduplication/expiry retains normalized history, original source fingerprints and delivery identities. Applications own policies, pure upcaster implementations, authorization and deliberate replay; no PII-processing or automatic provider resend is included. See payload lifecycle and schema evolution.

RevenueEventBackfillService implements Core's IRevenueEventBackfill. Explicit scope/consumer/UUID range jobs create only missing original-ID outboxes in bounded pages; new deliveries, checkpoint and command receipt share one atomic commit. Existing delivery states/history remain unchanged. Same-command lost-response replay and concurrent pages/jobs are supported. Malformed/future history aborts before page writes. This is a live range scan: start another job to discover inserts behind an already committed cursor. See usage and limits.

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

Showing the top 5 NuGet packages that depend on RevenueFlow.Events:

Package Downloads
RevenueFlow.Analytics

Idempotent commerce analytics, scoped reports and recoverable scheduled exports.

RevenueFlow.Customers

Provider-neutral scoped commerce building blocks for .NET.

RevenueFlow.Management

Scoped bounded commerce management, identity links and explicit event delivery recovery.

RevenueFlow.SelfService

Durable customer center selections, provider controls, retention and billing reminders.

RevenueFlow

RevenueFlow commerce composition with internal administrative issuance. External providers and stores are explicit opt-ins.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
0.1.0-alpha.7.2 99 11/10/2026