EventFlow 0.80.4377

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package EventFlow --version 0.80.4377                
NuGet\Install-Package EventFlow -Version 0.80.4377                
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="EventFlow" Version="0.80.4377" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add EventFlow --version 0.80.4377                
#r "nuget: EventFlow, 0.80.4377"                
#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.
// Install EventFlow as a Cake Addin
#addin nuget:?package=EventFlow&version=0.80.4377

// Install EventFlow as a Cake Tool
#tool nuget:?package=EventFlow&version=0.80.4377                

Async/await first CQRS+ES and DDD framework for .NET - https://docs.geteventflow.net/

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp1.0 was computed.  netcoreapp1.1 was computed.  netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 is compatible.  netcoreapp3.1 is compatible. 
.NET Standard netstandard1.6 is compatible.  netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net452 is compatible.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen30 was computed.  tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (19)

Showing the top 5 NuGet packages that depend on EventFlow:

Package Downloads
EventFlow.AspNetCore

AspNetCore support for EventFlow

EventFlow.Sql

# EventFlow ![EventFlow logo](./icon-128.png) ``` $ dotnet add package EventFlow ``` EventFlow is a basic CQRS+ES framework designed to be easy to use. Have a look at our [getting started guide](https://docs.geteventflow.net/GettingStarted.html), the [do’s and don’ts](https://docs.geteventflow.net/DosAndDonts.html) and the [FAQ](https://docs.geteventflow.net/FAQ.html). ## Features * **Easy to use**: Designed with sensible defaults and implementations that make it easy to create an example application * **Highly configurable and extendable**: EventFlow uses interfaces for every part of its core, making it easy to replace or extend existing features with custom implementation * **No use of threads or background workers** * **MIT licensed** Easy to understand and use license for enterprise ## Versions Development of version 1.0 has started and is mainly braking changes regarding changes related to replacing EventFlow types with that of Microsoft extension abstractions, mainly `IServiceProvider` and `ILogger<>`. The following list key characteristics of each version as well as its related branches (not properly configured yet). * `1.x` Represents the next iteration of EventFlow that aligns EventFlow with the standard packages for .NET (Core). Releases here will only support .NET Standard, .NET Core and .NET versions going forward. - Released - Still development - Not all projects migrated yet Read the [migration guide](./MIGRATION_GUIDE.md) to view the full list of breaking changes as well as recommendations on how to migrate. ### Documentation (not complete) Version 1.x documentation has been pulled into this repository in order to have the code and documentation closer together and (hopefully) have the documentation updated in the same pull-requests as any code changes. ### NuGet package status - 🟢 ported - 💚 newly added to 1.0 - 🟠 not yet ported to 1.0 - 💀 for packages that are removed as part of 1.0 (see the [migration guide](./MIGRATION_GUIDE.md) for details) Projects - 🟢 `EventFlow` - 🟠 `EventFlow.AspNetCore` - 💀 `EventFlow.Autofac` - 💀 `EventFlow.DependencyInjection` - 🟠 `EventFlow.Elasticsearch` - 🟠 `EventFlow.EntityFramework` - 🟠 `EventFlow.EventStores.EventStore` - 🟢 `EventFlow.Hangfire` - 🟢 `EventFlow.MongoDB` - 🟢 `EventFlow.MsSql` - 💀 `EventFlow.Owin` - 🟢 `EventFlow.PostgreSql` - 💚 `EventFlow.Redis` - 🟠 `EventFlow.RabbitMQ` - 🟢 `EventFlow.Sql` - 🟠 `EventFlow.SQLite` - 🟢 `EventFlow.TestHelpers` ### Branches - `develop-v1`: Development branch, pull requests should be done here - `release-v1`: Release branch, merge commits are done to this branch from `develop-v1` to create releases. Typically each commit represents a release * `0.x` (legacy) The current stable version of EventFlow and has been the version of EventFlow for almost six years. 0.x versions have .NET Framework support and limited support to the Microsoft extension packages through extra NuGet packages. Feature and bug fix releases will still be done while there's interest in the community. ### Branches - `develop-v0`: Development branch, pull requests should be done here - `release-v0`: Release branch, merge commits are done to this branch from `develop-v0` to create releases. Typically each commit represents a release ### Documentation Version 0.x documentation is (although a bit outdated) is live at https://docs.geteventflow.net/. ## Talks directly related to EventFlow - [GOTO Aarhus 2022](https://github.com/rasmus/presentation-goto-2022) by [rasmus](https://github.com/rasmus) Practical event sourcing using EventFlow

EventFlow.DependencyInjection

Microsoft.Extensions.DependencyInjection support for EventFlow

EventFlow.Elasticsearch

Elasticsearch support for EventFlow

EventFlow.MongoDB

# EventFlow ![EventFlow logo](./icon-128.png) ``` $ dotnet add package EventFlow ``` EventFlow is a basic CQRS+ES framework designed to be easy to use. Have a look at our [getting started guide](https://docs.geteventflow.net/GettingStarted.html), the [do’s and don’ts](https://docs.geteventflow.net/DosAndDonts.html) and the [FAQ](https://docs.geteventflow.net/FAQ.html). ## Features * **Easy to use**: Designed with sensible defaults and implementations that make it easy to create an example application * **Highly configurable and extendable**: EventFlow uses interfaces for every part of its core, making it easy to replace or extend existing features with custom implementation * **No use of threads or background workers** * **MIT licensed** Easy to understand and use license for enterprise ## Versions Development of version 1.0 has started and is mainly braking changes regarding changes related to replacing EventFlow types with that of Microsoft extension abstractions, mainly `IServiceProvider` and `ILogger<>`. The following list key characteristics of each version as well as its related branches (not properly configured yet). * `1.x` Represents the next iteration of EventFlow that aligns EventFlow with the standard packages for .NET (Core). Releases here will only support .NET Standard, .NET Core and .NET versions going forward. - Released - Still development - Not all projects migrated yet Read the [migration guide](./MIGRATION_GUIDE.md) to view the full list of breaking changes as well as recommendations on how to migrate. ### Documentation (not complete) Version 1.x documentation has been pulled into this repository in order to have the code and documentation closer together and (hopefully) have the documentation updated in the same pull-requests as any code changes. ### NuGet package status - 🟢 ported - 💚 newly added to 1.0 - 🟠 not yet ported to 1.0 - 💀 for packages that are removed as part of 1.0 (see the [migration guide](./MIGRATION_GUIDE.md) for details) Projects - 🟢 `EventFlow` - 🟠 `EventFlow.AspNetCore` - 💀 `EventFlow.Autofac` - 💀 `EventFlow.DependencyInjection` - 🟠 `EventFlow.Elasticsearch` - 🟠 `EventFlow.EntityFramework` - 🟠 `EventFlow.EventStores.EventStore` - 🟢 `EventFlow.Hangfire` - 🟢 `EventFlow.MongoDB` - 🟢 `EventFlow.MsSql` - 💀 `EventFlow.Owin` - 🟢 `EventFlow.PostgreSql` - 💚 `EventFlow.Redis` - 🟠 `EventFlow.RabbitMQ` - 🟢 `EventFlow.Sql` - 🟠 `EventFlow.SQLite` - 🟢 `EventFlow.TestHelpers` ### Branches - `develop-v1`: Development branch, pull requests should be done here - `release-v1`: Release branch, merge commits are done to this branch from `develop-v1` to create releases. Typically each commit represents a release * `0.x` (legacy) The current stable version of EventFlow and has been the version of EventFlow for almost six years. 0.x versions have .NET Framework support and limited support to the Microsoft extension packages through extra NuGet packages. Feature and bug fix releases will still be done while there's interest in the community. ### Branches - `develop-v0`: Development branch, pull requests should be done here - `release-v0`: Release branch, merge commits are done to this branch from `develop-v0` to create releases. Typically each commit represents a release ### Documentation Version 0.x documentation is (although a bit outdated) is live at https://docs.geteventflow.net/. ## Talks directly related to EventFlow - [GOTO Aarhus 2022](https://github.com/rasmus/presentation-goto-2022) by [rasmus](https://github.com/rasmus) Practical event sourcing using EventFlow

GitHub repositories (2)

Showing the top 2 popular GitHub repositories that depend on EventFlow:

Repository Stars
twzhangyang/RestAirline
DDD+CQRS+EventSourcing+Hypermedia API+ASP.NET Core 3.1+Masstransit+terraform+docker+k8s
OKTAYKIR/EventFlow.Example
DDD+CQRS+Event-sourcing examples using EventFlow following CQRS-ES architecture. It is configured with RabbitMQ, MongoDB(Snapshot store), PostgreSQL(Read store), EventStore(GES). It's targeted to .Net Core 2.2 and include docker compose file.
Version Downloads Last updated
1.0.5004-alpha 1,406 5/23/2024
1.0.5003-alpha 12,528 6/21/2023
1.0.5002-alpha 4,449 11/11/2022
1.0.5001-alpha 2,293 3/15/2022
1.0.4748-alpha 16,050 9/9/2021
1.0.4617-alpha 1,697 6/11/2021
0.83.4713 1,077,126 9/7/2021
0.82.4684 8,003 8/30/2021
0.82.4659 36,826 6/17/2021
0.81.4483 170,894 12/14/2020
0.80.4377 51,671 10/1/2020
0.79.4216 122,378 5/13/2020
0.78.4205 5,824 5/11/2020
0.77.4077 93,706 12/10/2019
0.76.4014 33,884 10/19/2019
0.75.3970 12,417 9/12/2019
0.74.3948 24,015 7/1/2019
0.73.3933 9,470 6/11/2019
0.72.3914 11,656 5/28/2019
0.71.3834 14,890 4/17/2019
0.70.3824 6,880 4/11/2019
0.69.3772 17,194 2/12/2019
0.68.3728 46,021 12/3/2018
0.67.3697 12,869 10/14/2018
0.66.3673 8,642 9/28/2018
0.65.3664 10,618 9/22/2018
0.64.3598 10,244 8/27/2018
0.63.3581 9,175 8/7/2018
0.62.3569 35,196 7/5/2018
0.61.3524 6,499 6/26/2018
0.60.3490 5,388 6/18/2018
0.59.3396 6,116 5/23/2018
0.58.3377 5,146 5/13/2018
0.57.3359 5,865 4/30/2018
0.56.3328 4,581 4/24/2018
0.55.3323 4,735 4/24/2018
0.54.3261 6,125 2/25/2018
0.53.3204 4,645 1/25/2018
0.52.3178 5,356 11/2/2017
0.51.3155 4,217 10/25/2017
0.50.3124 4,303 10/21/2017
0.49.3031 6,841 9/7/2017
0.48.2937 5,443 7/11/2017
0.47.2894 4,922 6/28/2017
0.46.2886 7,841 5/29/2017
0.45.2877 4,372 5/28/2017
0.44.2832 4,202 5/12/2017
0.43.2806 2,351 5/5/2017
0.42.2755 5,046 5/2/2017
0.41.2727 4,927 4/27/2017
0.40.2590 8,133 3/30/2017
0.39.2553 5,181 1/16/2017
0.38.2454 5,041 12/2/2016
0.37.2424 5,244 11/8/2016
0.36.2315 6,213 10/18/2016
0.35.2247 5,119 9/6/2016
0.34.2221 4,892 8/23/2016
0.33.2190 4,650 8/16/2016
0.32.2163 4,810 7/4/2016
0.31.2106 4,633 6/30/2016
0.30.2019 4,977 6/16/2016
0.29.1973 6,393 4/19/2016
0.28.1852 4,700 4/5/2016
0.27.1765 8,030 2/25/2016
0.26.1714 4,678 2/20/2016
0.25.1695 3,985 2/15/2016
0.24.1563 4,360 1/25/2016
0.23.1470 5,008 12/5/2015
0.22.1393 4,868 11/19/2015
0.21.1312 4,140 10/26/2015
0.20.1274 3,943 10/22/2015
0.19.1225 3,851 10/19/2015
0.18.1181 4,212 10/7/2015
0.17.1134 4,090 9/28/2015
0.16.1120 3,989 9/27/2015
0.15.1057 4,070 9/24/2015
0.14.1051 4,031 9/23/2015
0.13.962 3,991 9/13/2015
0.12.891 3,792 9/4/2015
0.11.751 3,752 8/24/2015
0.10.642 3,537 8/17/2015
0.9.580 3,609 7/20/2015
0.8.560 3,423 5/29/2015
0.7.481 3,412 5/22/2015
0.6.456 3,247 5/18/2015
0.5.390 3,423 5/8/2015
0.4.353 3,296 5/5/2015
0.3.292 3,821 4/30/2015

Breaking: To support .NET going forward, all EventFlow test have been converted
from .NET Framework 4.x to .NET Core 3.1. This however, introduced a set of
breaking changes
* EntityFramework has been updated from 2.2.6 to 3.1.5
* `IHangfireJobRunner.Execute` is now `IHangfireJobRunner.ExecuteAsync`
Breaking: Merged `AggregateReadStoreManager` and `SingleAggregateReadStoreManager`
into one class in order to always guarantee in-order event processing
Breaking: Marked the `UseReadStoreFor<,,,>` configuration methods as obsolete,
in favor of the simpler overloads with less type parameters (as those automatically
figure out the AggregateRoot and Id types and configure the more reliable
`SingleAggregateReadStoreManager` implementation)
Obsolete: The class `AsyncHelper` and all non-async methods using it have been
marked obsolete and will be removed in EventFlow 1.0 (not planned yet). If you rely
on these non-async methods, then merely copy-paste the `AsyncHelper` from the EventFlow
code base and continue using it in your transition to async only
Fixed: An issue where `EntityFrameworkEventPersistence` could possibly save aggregate
events out of order, which would lead to out-of-order application when streaming events
ordered by GlobalSequenceNumber
New: `FilesEventPersistence` now uses relative paths
New: A new set of hook-in interfaces are provided from this release, which should
make it easier to implement crash resilience (#439) in EventFlow. Please note that
this new API is experimentational and subject to change as different strategies are
implemented
* `IAggregateStoreResilienceStrategy`
* `IDispatchToReadStoresResilienceStrategy`
* `IDispatchToSubscriberResilienceStrategy`
* `ISagaUpdateResilienceStrategy`