Welcome to EventFlow’s documentation!

EventFlow is a basic CQRS+ES framework designed to be easy to use.

Have a look at our getting started guide, the do’s and don’ts and the FAQ.

Contents:

• Getting started
  • Example application
  • Aggregate identity
  • Aggregate
  • Event
  • Command
  • Command handler
  • Read model
  • Next steps

Basics

• Identity
• Aggregates
  • Events
  • Emitting events
  • Applying events
• Commands
  • Execution results
  • Ensure idempotency
• Subscribers
  • Synchronous subscribers
  • Asynchronous subscribers
  • Subscribe to every event
• Metadata
  • Custom metadata provider
  • Additional built-in providers
• Queries
  • Queries shipped with EventFlow
• Sagas
  • Alternative saga store
• Jobs
  • Create your own jobs
  • Hangfire
• Event upgrade
  • Example - removing a damaged event
  • Example - replace event

Stores

• Event stores
  • In-memory
  • MSSQL event store
  • PostgreSql event store
  • Mongo DB
  • Files
• Read model stores
  • Creating read models
  • Read model locators
  • Read store implementations

Integration

• Microsoft SQL Server
• PostgreSql
• RabbitMQ

Additional reading

• Configuration
• IoC container
  • Autofac
• Log
• Snapshots
  • Snapshot strategy
  • Upgrading snapshots
  • Snapshot store implementations
• Customize
  • Decorating implementations
  • Registering new implementations
• Event serialization and value objects
  • Making pretty and clean JSON
• Do’s and don’ts
  • Business rules
  • Events
• Specifications
• FAQ - frequently asked questions
  • How can I ensure that only specific users can execute commands?
  • Why isn’t there a “global sequence number” on domain events?
  • Why doesn’t EventFlow have a unit of work concept?
  • Why are subscribers receiving events out of order?

Indices and tables

• Index
• Search Page