Skip to Content

Changes for page Synchronous Routing

Last modified by Martijn Woudstra on 2023/04/13 15:33
From version 30.1
edited by Martijn Woudstra
on 2023/04/13 15:33
Change comment: Imported from XAR
To version 28.1
edited by Martijn Woudstra
on 2022/08/25 14:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -31,7 +31,7 @@
31 31  * You need to deploy the complete five layers at once to prevent timeouts while deploying half of your solution
32 32  * In contrast with asynchronous routing the synchronous routing only has one output tied to an input (instead of a possible one towards many)
33 33  
34 -If you want to learn more about asynchronous routing instead of synchronous routing, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-asynchronous-routing||target="blank"]]. In synchronous routing, you not only route messages towards a certain offramp. On top of that, the routing waits for a response. Subsequently, it will route the message back to the correct onramp from which the message originated. This process happens based on a header value that is automatically determined and set by eMagiz.
34 +If you want to learn more about asynchronous routing instead of synchronous routing, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-asynchronous-routing.WebHome||target="blank"]]. In synchronous routing, you not only route messages towards a certain offramp. On top of that, the routing waits for a response. Subsequently, it will route the message back to the correct onramp from which the message originated. This process happens based on a header value that is automatically determined and set by eMagiz.
35 35  
36 36  === 3.1 Make a decision ===
37 37