EventFlow 0.18.1181
Prefix ReservedSee the version list below for details.
dotnet add package EventFlow --version 0.18.1181
NuGet\Install-Package EventFlow -Version 0.18.1181
<PackageReference Include="EventFlow" Version="0.18.1181" />
paket add EventFlow --version 0.18.1181
#r "nuget: EventFlow, 0.18.1181"
// Install EventFlow as a Cake Addin #addin nuget:?package=EventFlow&version=0.18.1181 // Install EventFlow as a Cake Tool #tool nuget:?package=EventFlow&version=0.18.1181
CQRS+ES framework
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net451 is compatible. net452 was computed. 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. |
-
- Newtonsoft.Json (>= 7.0.1)
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 | 849 | 5/23/2024 |
1.0.5003-alpha | 9,202 | 6/21/2023 |
1.0.5002-alpha | 3,669 | 11/11/2022 |
1.0.5001-alpha | 2,225 | 3/15/2022 |
1.0.4748-alpha | 15,483 | 9/9/2021 |
1.0.4617-alpha | 1,642 | 6/11/2021 |
0.83.4713 | 1,007,776 | 9/7/2021 |
0.82.4684 | 7,829 | 8/30/2021 |
0.82.4659 | 35,848 | 6/17/2021 |
0.81.4483 | 164,559 | 12/14/2020 |
0.80.4377 | 50,995 | 10/1/2020 |
0.79.4216 | 120,757 | 5/13/2020 |
0.78.4205 | 5,641 | 5/11/2020 |
0.77.4077 | 93,441 | 12/10/2019 |
0.76.4014 | 33,680 | 10/19/2019 |
0.75.3970 | 12,243 | 9/12/2019 |
0.74.3948 | 23,764 | 7/1/2019 |
0.73.3933 | 9,336 | 6/11/2019 |
0.72.3914 | 11,484 | 5/28/2019 |
0.71.3834 | 14,714 | 4/17/2019 |
0.70.3824 | 6,684 | 4/11/2019 |
0.69.3772 | 17,012 | 2/12/2019 |
0.68.3728 | 45,862 | 12/3/2018 |
0.67.3697 | 12,723 | 10/14/2018 |
0.66.3673 | 8,428 | 9/28/2018 |
0.65.3664 | 10,446 | 9/22/2018 |
0.64.3598 | 10,113 | 8/27/2018 |
0.63.3581 | 8,996 | 8/7/2018 |
0.62.3569 | 35,044 | 7/5/2018 |
0.61.3524 | 6,303 | 6/26/2018 |
0.60.3490 | 5,215 | 6/18/2018 |
0.59.3396 | 5,969 | 5/23/2018 |
0.58.3377 | 4,999 | 5/13/2018 |
0.57.3359 | 5,725 | 4/30/2018 |
0.56.3328 | 4,485 | 4/24/2018 |
0.55.3323 | 4,619 | 4/24/2018 |
0.54.3261 | 6,010 | 2/25/2018 |
0.53.3204 | 4,547 | 1/25/2018 |
0.52.3178 | 5,262 | 11/2/2017 |
0.51.3155 | 4,111 | 10/25/2017 |
0.50.3124 | 4,180 | 10/21/2017 |
0.49.3031 | 6,735 | 9/7/2017 |
0.48.2937 | 5,348 | 7/11/2017 |
0.47.2894 | 4,826 | 6/28/2017 |
0.46.2886 | 7,670 | 5/29/2017 |
0.45.2877 | 4,282 | 5/28/2017 |
0.44.2832 | 4,137 | 5/12/2017 |
0.43.2806 | 2,330 | 5/5/2017 |
0.42.2755 | 4,931 | 5/2/2017 |
0.41.2727 | 4,812 | 4/27/2017 |
0.40.2590 | 8,013 | 3/30/2017 |
0.39.2553 | 5,060 | 1/16/2017 |
0.38.2454 | 4,905 | 12/2/2016 |
0.37.2424 | 5,099 | 11/8/2016 |
0.36.2315 | 6,084 | 10/18/2016 |
0.35.2247 | 5,017 | 9/6/2016 |
0.34.2221 | 4,763 | 8/23/2016 |
0.33.2190 | 4,532 | 8/16/2016 |
0.32.2163 | 4,699 | 7/4/2016 |
0.31.2106 | 4,505 | 6/30/2016 |
0.30.2019 | 4,861 | 6/16/2016 |
0.29.1973 | 6,259 | 4/19/2016 |
0.28.1852 | 4,563 | 4/5/2016 |
0.27.1765 | 7,914 | 2/25/2016 |
0.26.1714 | 4,538 | 2/20/2016 |
0.25.1695 | 3,893 | 2/15/2016 |
0.24.1563 | 4,267 | 1/25/2016 |
0.23.1470 | 4,918 | 12/5/2015 |
0.22.1393 | 4,772 | 11/19/2015 |
0.21.1312 | 4,033 | 10/26/2015 |
0.20.1274 | 3,836 | 10/22/2015 |
0.19.1225 | 3,758 | 10/19/2015 |
0.18.1181 | 4,112 | 10/7/2015 |
0.17.1134 | 3,998 | 9/28/2015 |
0.16.1120 | 3,889 | 9/27/2015 |
0.15.1057 | 3,959 | 9/24/2015 |
0.14.1051 | 3,935 | 9/23/2015 |
0.13.962 | 3,911 | 9/13/2015 |
0.12.891 | 3,707 | 9/4/2015 |
0.11.751 | 3,690 | 8/24/2015 |
0.10.642 | 3,464 | 8/17/2015 |
0.9.580 | 3,541 | 7/20/2015 |
0.8.560 | 3,364 | 5/29/2015 |
0.7.481 | 3,352 | 5/22/2015 |
0.6.456 | 3,190 | 5/18/2015 |
0.5.390 | 3,371 | 5/8/2015 |
0.4.353 | 3,230 | 5/5/2015 |
0.3.292 | 3,727 | 4/30/2015 |
POTENTIAL DATA LOSS for the **files event store**: The EventFlow
internal functionality regarding event stores has been refactored resulting
in information regarding aggregate names being removed from the event
persistence layer. The files based event store no longer stores its events in
the path `[STORE PATH]\[AGGREGATE NAME]\[AGGREGATE ID]\[SEQUENCE].json`, but
in the path `[STORE PATH]\[AGGREGATE ID]\[SEQUENCE].json`. Thus if you are
using the files event store for tests, you should move the events into the
new file structure. Alternatively, implement the new `IFilesEventLocator` and
provide your own custom event file layout.
Breaking: Event stores have been split into two parts, the `IEventStore`
and the new `IEventPersistence`. `IEventStore` has the same interface before
but the implementation is now no longer responsible for persisting the events,
only converting and serializing the persisted events. `IEventPersistence`
handles the actual storing of events and thus if any custom event stores have
been implemented, they should implement to the new `IEventPersistence`
instead.
New: Added `IEntity`, `IEntity<>` and an optional `Entity<>` that developers
can use to implement DDD entities.