Timeline for CQRS async query from command handler
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 11, 2018 at 22:26 | comment | added | yogibear | It seems I would still need to solve that same problem when it comes to sagas, the saga may dispatch some action to ultimately sent the email once the order details have been retrieved, but it would need to track and correlate the original message relating to the order detail query in order to determine the reason for querying the order to begin with. Would that generally be managed by some in memory queue of prior events or commands that are part of a 'live' process? | |
| Mar 11, 2018 at 22:19 | comment | added | yogibear | Thanks for your response, I think with the saga or process manager patterns my problem still remains in that I'm unsure of what sort of mechanism to use to essentially 'resume' a process asynchronously. The order details are stored in a different service to the communications service (which is responsible for sending the emails) and so when we view the execution of the process to send the order confirmation email - that thread will need to halt execution when it dispatches the async request to retrieve order details and then resume where it left off once those details have been retrieved. | |
| Mar 11, 2018 at 17:37 | history | answered | VoiceOfUnreason | CC BY-SA 3.0 |