Gone through article https://docs.particular.net/nservicebus/sagas/ about Saga, have some query about using SataData.
As per understanding, we can store some unique-id & status property related to saga & different message handled by saga can update SagaData property to update saga state & ultimately close saga once process get completed.
Can we store some business data(like date,int,string columns) which required to send data from saga to other handler for processing ?
Can we store business data containing multiple fields in Json format ? scenario for this is,
we are using aggregator pattern (https://www.enterpriseintegrationpatterns.com/patterns/messaging/Aggregator.html) to aggregate Json data(which added as SagaData property) from multiple message & aggregate them & send one message from saga
Note : 1. In any of the case we are not intent to query saga data from outside the saga
2. Once saga completed, we don’t intent to store that data for any future use so its OK if we loose all SagaData once saga get completed.
3. Using NSB 7 & SQL transport, using SQL for saga persistence