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.

Sign up for GitHub

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

Jump to bottom

Consider that aggregate might produce events as result of command processing which are not sourced by the same aggregate #140

Open
zambrovski opened this issue Sep 6, 2024 · 0 comments
Open

Consider that aggregate might produce events as result of command processing which are not sourced by the same aggregate #140

zambrovski opened this issue Sep 6, 2024 · 0 comments
Labels
Idea 💡 An idea we could follow up

Comments

@zambrovski
Copy link
Contributor

If all EventSourcingHandlers are in the same interface you have to implement them by the event-sourced aggregate and events will be de-serialized and delivered to the aggregate - even if the aggregate doesn't need it to restore the state for command handling.
@zambrovski zambrovski added the Idea 💡 An idea we could follow up label Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Idea 💡 An idea we could follow up
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zambrovski