Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic Aggregate Event Stream filtering #1589

Open
smcvb opened this issue Nov 4, 2020 · 1 comment
Open

Automatic Aggregate Event Stream filtering #1589

smcvb opened this issue Nov 4, 2020 · 1 comment
Labels
Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.

Comments

@smcvb
Copy link
Member

smcvb commented Nov 4, 2020

Enhancement Description

When retrieving a stream of events for a given aggregate, chances are high not all events in the stream will actually be used to source the aggregate. Adding the unused events as a filter for subsequent calls will make aggregate event stream retrieval more efficient. It does require specific implementations on the storage engines to actually store and use a provided filter.

Current Behaviour

Aggregate event streams are always completely retrieved without any filter.

Wanted Behaviour

Filter out unused events for sourcing the aggregate from the event stream on subsequent invocations.

@smcvb smcvb added Type: Enhancement Use to signal an issue enhances an already existing feature of the project. Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. labels Nov 4, 2020
@smcvb smcvb added this to the Release 4.5 milestone Nov 4, 2020
@smcvb smcvb removed this from the Release 4.5 milestone Jan 11, 2021
@smcvb
Copy link
Member Author

smcvb commented Dec 21, 2023

I believe the introduction of the Dynamic Consistency Boundary (DCB), as suggested in the presentation The Aggregate is dead! Long live the Aggregate!, will be of utmost importance to provide a way to easily filter events for any aggregate stream format.

Hence, I anticipate that once the DCB idea has matured more, that Axon Framework may just provide a similar solution.
Given that supporting the DCB will be a very (very!) rough change for the EventStore, it will very likely be an Axon Framework 5 feature.
Simply because of the breaking changes it'll introduce.

To that end, I have added this issue to milestone 5.0.0.
Note that this does not conclusively mean it'll be a part of 5.0.0, but rather part of the Axon Framework 5.x lifecycle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
Projects
None yet
Development

No branches or pull requests

1 participant