-
Notifications
You must be signed in to change notification settings - Fork 149
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
Aggregate event streams #664
Comments
Wrapping the event and passing the streamId as metadata to the event envelope (which also extends IEvent) may solve the problem. the event handler can be decorated as follow: @EventsHandler(Envelope<OriginalEvent>) (just started looking into nestjs and CQRS module... hope I'm not messing up) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a...
Current behavior
Persisting events using external stores such as Event Store happens by appending them to a stream. The stream groups all events related to a particular instance of an aggregate root. The stream name usually is
<AggregateRoot>-<id>
.At the moment, the stream name/id information has to be bundled with the event.
Expected behavior
It would be great to introduce the concept of stream name/id at the
AggregateRoot
levelSuch change would also impact
IEventBus
andIEventPublisher
interfacesEventPublisher
If
streamId
is optional, the change is non-breaking.The text was updated successfully, but these errors were encountered: