You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an example of cross module (bounded context) communication in the repo (order payment flow). The way it looks to me is that it is a choreography style saga (modules listen to each others integration events).
Has anyone been able to create an orchestration style saga (one process issues commands to the other modules)? Any ideas on how to implement this in the current code? Some of the issues i'm running into are:
Seems like this would require the saga to have a reference to the commands from the modules it is orchestrating (not good)
How would the commands be delivered from the saga to the other modules? Mediatr? Another message bus?
Would the Saga be a different Module altogether or live inside one of the existing modules?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey folks!
There is an example of cross module (bounded context) communication in the repo (order payment flow). The way it looks to me is that it is a choreography style saga (modules listen to each others integration events).
Has anyone been able to create an orchestration style saga (one process issues commands to the other modules)? Any ideas on how to implement this in the current code? Some of the issues i'm running into are:
Thanks
Beta Was this translation helpful? Give feedback.
All reactions