I have a long running process that collects together the IDs of Aggregates that have been edited/changed, so that a later command can 'publish' them to a legacy model.
I understand that I should use a kind of Saga for this which listens to certain events, then stores additional IDs for later processing.
The question I have, given I am in an event sourcing environment (using an event store for the aggregates), is how should I be expecting to store the actual saga data?
- Should I be emitting an event from the saga to be recorded in the event store?
- Should I have a separate persistence engine to store the data, like a MySQL instance?
I am confused as to how complicated it would be for option 1, but also, to have to create another data schema with a single table for option two seems overkill also.
What are others in the community doing in this kind of scenario?