Looking toward EventFlow v2

[rasmus]

While I have no specific plans for v2 of EventFlow, planning for it makes sense. Ideally it would properly make sense to align the release with the next .NET 10 LTS release as to use that to add .NET 10 support as well as remove support for the then deprecated .NET versions.

First off, as with any EventFlow release, care is taken to minimize the number of breaking changes and ensure no data migrations are needed. Systems built on EventFlow tend to be old, complicated and have enormous data volumes, thus its important for any user of EventFlow that upgrading to newer versions is easy and safe.

Here are some thoughts on what might be included in a v2 release (nothing is final!). Some are topics I have put off for doing for v1 as to keep the scope down a bit, others are ideas that have come up over the last couple of years.

• Create a EventFlow.Abstractions (or some other name) that contains e.g. the value objects (ValueObject and SingleValueObject) that developers have used outside EventFlow enabled projects. Typically, these have been used in e.g. "contract" packages and having the entire EventFlow package referenced severely bloats dependencies of what should be a simple contract.
• Finally, split Newtonsoft.Json out into a separate package and rely on System.Text.Json by default in the core package. There have been many issues and PRs on this and finally getting it done would be awesome. However, since many rely on this working perfectly today, it has to be carefully done in order to ensure existing setups continue to work.
• ReadModelLocator async support ReadModelLocator Task support? #1061
• Provide more metadata to snapshot upgraders Snapshot upgrader need metadata #919

I'll update this issue with ideas and suggestions if any are posted. If anyone have ideas, let me know.

[MMonrad]

Hello @rasmus,

If you have any interrest in getting help to version 2, I could have an interrest in giving a hand. Specially with the splitting of Newtonsoft.Json and System.Text.Json.