EventLoom
EventLoom is an opinionated event-sourcing framework for .NET 10. It gives applications explicit aggregates and events, a provider-neutral storage engine, and built-in providers for PostgreSQL, SQLite, and MongoDB.
flowchart LR
App[Application] --> Domain[Aggregates and events]
Domain --> Engine[EventLoom.Storage<br/>engine]
Engine --> Ef[EF Core provider]
Ef --> Postgres[PostgreSQL<br/>distributed production]
Ef --> Sqlite[SQLite<br/>local or single process]
Engine --> Mongo[MongoDB provider<br/>replica set or mongos]
Engine --> Workers[Projections and outbox]
Choose your next step
Section titled “Choose your next step”| I want to… | Start here |
|---|---|
| Evaluate EventLoom from this repository | Installation |
| Learn the event-sourcing programming model | Build your first aggregate |
| Choose a storage provider | Storage providers |
| Understand boundaries and guarantees | Architecture and Delivery model |
| Configure relational storage | Configure the EF Core store |
| Configure MongoDB storage | Use MongoDB |
| Build read models or external integration | Build projections and Publish integration messages |
| Run EventLoom in production | Deploy and recover |
The developer model
Section titled “The developer model”- Model business facts as immutable, versioned events.
- Change aggregate state only by applying those events.
- Append an event batch atomically with an expected stream version.
- Build read models and external integration from the committed event log.
The Aggregates and events concept explains why these boundaries matter. The Ordering API sample shows the complete application path in an ASP.NET Core service that can run on PostgreSQL or MongoDB.
What EventLoom provides
Section titled “What EventLoom provides”Aggregate<TId>for event-only state changes and replay through typedApply(TEvent)methods.- Stable event names and versions through
[EventType], explicit registration, and JSON serialization. - Deterministic JSON upcaster chains for changing persisted event schemas.
EventLoom.Storage, which contains the provider-neutral engine used by application code:EventStore,AggregateRepository<TAggregate, TId>,EventLoomUnitOfWork, projections, snapshots, and outbox administration.- Built-in storage providers:
EventLoom.EntityFrameworkCore.PostgreSqlfor distributed relational deployments;EventLoom.EntityFrameworkCore.Sqlitefor local, embedded, and controlled single-node use;EventLoom.MongoDbfor direct-driver MongoDB persistence on a replica set or sharded deployment.
- Optional required tenancy with a scoped
ITenantAccessor. - Checkpointed asynchronous projections, provider-transactional projections, explicitly registered inline projections, and a transactional outbox.
- A shared storage conformance suite that runs the same provider-neutral guarantees against every built-in provider.
Current status
Section titled “Current status”EventLoom is pre-release software. Version 0.1.0-alpha.0 is available from
NuGet; APIs and persistence
contracts may change before the first stable release. Check the
packages and compatibility reference and
configuration reference before relying on a feature
that affects persisted data or operational behavior.