RevenueFlow.Events.Abstractions
0.1.0-alpha.7.2
dotnet add package RevenueFlow.Events.Abstractions --version 0.1.0-alpha.7.2
NuGet\Install-Package RevenueFlow.Events.Abstractions -Version 0.1.0-alpha.7.2
<PackageReference Include="RevenueFlow.Events.Abstractions" Version="0.1.0-alpha.7.2" />
<PackageVersion Include="RevenueFlow.Events.Abstractions" Version="0.1.0-alpha.7.2" />
<PackageReference Include="RevenueFlow.Events.Abstractions" />
paket add RevenueFlow.Events.Abstractions --version 0.1.0-alpha.7.2
#r "nuget: RevenueFlow.Events.Abstractions, 0.1.0-alpha.7.2"
#:package RevenueFlow.Events.Abstractions@0.1.0-alpha.7.2
#addin nuget:?package=RevenueFlow.Events.Abstractions&version=0.1.0-alpha.7.2&prerelease
#tool nuget:?package=RevenueFlow.Events.Abstractions&version=0.1.0-alpha.7.2&prerelease
Business events and atomic outbox preparation
RevenueEventWrites.Prepare produces immutable history and per-consumer outbox writes. The caller must include these writes in the same AtomicCommitBatch as domain effects and command receipt. Consumer selection is frozen at event creation, bounded to 32 distinct ordinal IDs.
Event IDs are stable across redelivery. History and outbox schema version is 1. Consumer-specific outbox kinds isolate subscriptions; providers are not consumers and Core has no dispatch/store dependency.
RevenueBusinessEvent stores normalized fields and Data plus an optional owned RawPayload JSON object. Provider verification happens before persistence. The raw object is retained for inspection and reprocessing; it is not logged or treated as authority for scope/ownership. The complete serialized event must fit the store payload bound.
Optional DataSchemaVersion is omitted for legacy events; absence means version one. IRevenueEventReader provides a configured current view and original/projection provenance through bounded deterministic Data-only upcasters. Original source fingerprints survive explicit optional-raw compaction and expiry. See lifecycle and schema evolution for policies and recovery limits.
These contracts do not promise exactly-once external effects. Retain source economic identities, event IDs and receipts independently of optional payload retention. Management supports explicit replay of an expected terminal delivery with readable retained history. Core's IRevenueEventBackfill explicitly enrolls consumers in retained history through the durable Events implementation; adding a consumer alone does not start a backfill job.
| 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
- RevenueFlow.Core (>= 0.1.0-alpha.7.2)
- RevenueFlow.Stores.Abstractions (>= 0.1.0-alpha.7.2)
NuGet packages (12)
Showing the top 5 NuGet packages that depend on RevenueFlow.Events.Abstractions:
| Package | Downloads |
|---|---|
|
RevenueFlow.Events
Recoverable business-event history and per-consumer outbox dispatch. |
|
|
RevenueFlow.Commerce
Provider-neutral scoped commerce building blocks for .NET. |
|
|
RevenueFlow.Catalog
Catalog snapshot behavior and a development-only immutable catalog registry for RevenueFlow. |
|
|
RevenueFlow.Payments
Provider-neutral durable payment operations and verified purchase intake orchestration. |
|
|
RevenueFlow.Customers
Provider-neutral scoped commerce building blocks for .NET. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.1.0-alpha.7.2 | 144 | 11/10/2026 |