# eventflow/EventFlow

Async/await first CQRS+ES and DDD framework for .NET

Repository: https://github.com/eventflow/EventFlow
Canonical: https://ross.abutalabs.com/products/eventflow
Homepage: https://geteventflow.net
Language: C#
License: NOASSERTION
License Family: other
Topics: eventsourcing, cqrs, dotnet, async-await, eventstore, events, elasticsearch, rabbitmq, sagas, domain-driven-design, ddd, c-sharp, cqrs-es, framework, nuget, netstandard, event-sourcing, dotnet-core, netcore
Last push: 2026-07-31T10:37:33+00:00

## Health v2 (maintenance only)
Score: 80/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 95, release rhythm 48, longevity 100
- inputs: {"age_days": 4187, "days_push": 33, "days_rel": 270, "gap_med": 67.5, "n_releases_24m": 7}
- flags: no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2564, forks 469 (observed 2026-08-28T04:07:01.069790+00:00)

## What it is
EventFlow is an async/await-first CQRS and event sourcing framework for .NET, built around domain-driven design concepts like aggregates, commands, events, sagas, and read models. It is highly configurable via interfaces and ships with integration packages for event stores and infrastructure such as MSSQL, PostgreSQL, SQLite, MongoDB, RabbitMQ, Elasticsearch, and EventStore.

## Use cases
- build a CQRS application in .NET
- implement event sourcing for domain aggregates
- model a DDD domain with commands and events
- implement sagas and process managers
- store events in SQL Server, PostgreSQL, or MongoDB
- publish domain events to RabbitMQ
- project read models into Elasticsearch
- add snapshots and event upgraders to an event-sourced system

## When to choose
- you are building a .NET application using CQRS and event sourcing
- you want a DDD-oriented framework with sensible defaults and deep extensibility
- you need pluggable event store and message broker integrations
- you prefer async/await-first design with no background threads

## When to avoid
- you need a simple CRUD application without event sourcing
- you are not on the .NET ecosystem
- you need built-in command authorization out of the box
- you require all integration packages fully ported to the 1.x version line

## Facets
- artifact type: framework
- maturity: active
- function: web-framework, middleware, message-queue, search-engine, database, developer-tools
- domain: backend, web-development, developer-tools, microservices, apis
- platform: dotnet, cross-platform, windows
- tags: cqrs, event-sourcing, ddd, domain-driven-design, sagas, async-await, event-store, aggregates, read-models, snapshots, nuget, linux, macos

## Member repositories
- eventflow/EventFlow (main) score 80

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:01.069790+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:23:27.483817+00:00, confidence not recorded.
  - readme: https://github.com/eventflow/EventFlow (fetched 2026-08-28T04:07:01.069790+00:00, sha 67778f69e9ae)
  - homepage: https://geteventflow.net (fetched 2026-08-29T10:05:56.848185+00:00, sha 30c4c89460c3)
  - site_page: https://geteventflow.net/getting-started (fetched 2026-08-29T10:05:56.857016+00:00, sha 96bc10f41373)
  - site_page: https://geteventflow.net/additional/faq (fetched 2026-08-29T10:05:56.859098+00:00, sha 2edb549043e3)
- Data as of 2026-08-30T08:39:29.467469+00:00.