Event loading as a separate task as processing it onto the read side

eventflow / EventFlow

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

https://docs.geteventflow.net/

Other

2.33k stars 442 forks source link

Event loading as a separate task as processing it onto the read side #987

Closed kyle-bradley closed 1 year ago

kyle-bradley commented 1 year ago

In production with 100k+ events, having it pull all the events into memory first before applying them to the read side causes a lengthy processing time as well as high memory usage.

Also, populate doesn't have built-in "Rebuild" capabilities to process multiple read models at the same time.

rasmus commented 1 year ago

@kyle-bradley Awesome! could you update the release notes as well to ensure that developers know about this? ❤️

kyle-bradley commented 1 year ago

Will do - I also see that my unit test failed. I did a final load test and forgot to revert. Will fix that in a bit.

CLAassistant commented 1 year ago

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 3 committers have signed the CLA.

:white_check_mark: kyle-bradley
:white_check_mark: rasmus
:x: dependabot[bot]
_{You have signed the CLA already but the status is still pending? Let us recheck it.}