Great job Gary! By the way, are you going to show negative scenarios? For example, what happens if it fails to create a PDF file, will that stop your entire queue or those messages will be moved to another queue. I think it will be useful to show.
I have weird situation. When i call dispatch inside already dispatched message handler, my messenger goes into infinite loop and it handles my first message in the loop. I have tried different with Methods, or, like, after current message dispatched strategy, but... No results...the same loop. Maybe its because of using the same command bus instead event bus ? ( Inside handled message)
There's really no point in having two buses in this application. It was just to show how to set up separate buses for commands and events for scenarios where you want to handle them differently. It was really just an example for the sake of it.
@@GaryClarkeTech thanks for the great course :) I was wondering if handlers can be assigned to separate buses? Or if some internal events are resized on the busses, it would be good to have a practical example that is resolved with two separate busses
Great job Gary! By the way, are you going to show negative scenarios? For example, what happens if it fails to create a PDF file, will that stop your entire queue or those messages will be moved to another queue. I think it will be useful to show.
Yes Sergei..the next couple of videos cover retries and failure queues
I have weird situation.
When i call dispatch inside already dispatched message handler, my messenger goes into infinite loop and it handles my first message in the loop. I have tried different with Methods, or, like, after current message dispatched strategy, but... No results...the same loop. Maybe its because of using the same command bus instead event bus ? ( Inside handled message)
Sounds strange...have you tried pulling my branch and comparing it with yours?
@@GaryClarkeTech no, I was coding with you. But, my code, not along you:)
I did not understand the reasoning for having two buses. Is it just for logging purposes?
There's really no point in having two buses in this application. It was just to show how to set up separate buses for commands and events for scenarios where you want to handle them differently. It was really just an example for the sake of it.
@@GaryClarkeTech thanks for the great course :) I was wondering if handlers can be assigned to separate buses?
Or if some internal events are resized on the busses, it would be good to have a practical example that is resolved with two separate busses