Hi there, I may have misread the documentation, but something puzzles me:
I have a financial transaction, which in certain cases needs some post processing. The post processing needed is fairly simple: It’s a matter of calling a few commands on the transaction aggregate. Depending on the outcome of the commands, events are raised accordingly. To me sagas seem like the obvious solution.
A saga is created upon creation of the transaction aggregate (An event is raised containing the aggregate identifier). So far so good. Now, I realize that I can create a unique identifier for each post processing task, and associate it with the saga. However, this seems a bit like overkill, since the post processing does not operate across aggregates.
Is it possible somehow, to simply associate a saga with the aggregate identifier once, and then subscribe to which ever aggregate event I choose in the saga (Much like the eventlisteners on the aggregate)?
Yes, I could do this by explicitly putting the aggregate identifier on each relevant event, and set is as associationProperty on each listener in the saga, but it seems kind of redundant to raise events containing the aggregate identifier from within the aggregate it self