Skip to Content

Changes for page Messaging Synchronous

Last modified by Danniar Firdausy on 2024/09/16 13:37
From version 5.1
edited by Erik Bakker
on 2022/08/23 10:04
Change comment: There is no comment for this version
To version 9.1
edited by Erik Bakker
on 2023/01/23 08:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -5,9 +5,6 @@
5 5  
6 6  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
8 -* Last update: August 5th, 2021
9 -* Required reading time: 5 minutes
10 -
11 11  == 1. Prerequisites ==
12 12  
13 13  * Intermediate knowledge of the eMagiz platform
... ... @@ -35,7 +35,7 @@
35 35  * Messages have a time limit. The response needs to be back within 25 seconds (eMagiz default)
36 36  * Uses a request-response structure that talks to one system at a time
37 37  
38 -With this method, the sending party supplies the data to eMagiz via a push mechanism. eMagiz, in turn, places the data on a queue (in most cases an onramp queue). The subsequent process (the onramp) will process the message and will put the message on the next queue (the synchronous routing). That process will route each message to the correct offramp. This process continues until the message eMagiz delivers to the external system. At that point, eMagiz will wait for a response. If that response is received, the message will travel back to the starting point to deliver the reaction to the caller. If something goes wrong, for example, a timeout, the error message is also given back to the caller, and eMagiz will log the exception. If you want to learn more on that, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Understanding Error Handling.intermediate-understanding-error-handling-in-emagiz-messaging-synchronous.WebHome||target="blank"]].
35 +With this method, the sending party supplies the data to eMagiz via a push mechanism. eMagiz, in turn, places the data on a queue (in most cases an onramp queue). The subsequent process (the onramp) will process the message and will put the message on the next queue (the synchronous routing). That process will route each message to the correct offramp. This process continues until the message eMagiz delivers to the external system. At that point, eMagiz will wait for a response. If that response is received, the message will travel back to the starting point to deliver the reaction to the caller. If something goes wrong, for example, a timeout, the error message is also given back to the caller, and eMagiz will log the exception. If you want to learn more on that, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Understanding Error Handling.intermediate-understanding-error-handling-in-emagiz-messaging-synchronous||target="blank"]].
39 39  
40 40  [[image:Main.Images.Microlearning.WebHome@intermediate-key-concepts-emagiz-messaging-messaging-synchronous--concept.png]]
41 41  
... ... @@ -55,31 +55,30 @@
55 55  
56 56  === 3.2 Asynchronous vs Synchronous ===
57 57  
58 -The decision to handle an integration process in a specific manner depends on various relevant business and technical checks and balances that should be answered before choosing which integration pattern to choose and then subsequently which alternative method within an integration pattern to choose. If you want more information on how to decide this correctly, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Discover your integration landscape.intermediate-discover-your-integration-landscape-determining-integration-pattern.WebHome||target="blank"]] [microlearning](intermediate-discover-your-integration-landscape-determining-integration-pattern.md)
55 +The decision to handle an integration process in a specific manner depends on various relevant business and technical checks and balances that should be answered before choosing which integration pattern to choose and then subsequently which alternative method within an integration pattern to choose. If you want more information on how to decide this correctly, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Discover your integration landscape.intermediate-discover-your-integration-landscape-determining-integration-pattern.WebHome||target="blank"]].
59 59  
60 60  == 4. Assignment ==
61 61  
62 -No assignment accompanies this microlearning.
59 +Analyze a synchronous messaging flow from entry to exit and learn what happens within this process.
60 +This assignment can be completed with the help of your (Academy) project you have created/used in the previous assignment.
63 63  
64 64  == 5. Key takeaways ==
65 65  
66 -* The key aspects are:
67 - * Entry is the starting point of the integration process in messaging
68 - * Queues are an internal resource of eMagiz
69 - * Outside parties are not allowed to write on eMagiz queues directly
70 - * eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
64 +* Synchronous messaging is the less used, the less advised option when implementing a messaging integration via eMagiz
65 +* Key characteristics of synchronous messaging are:
66 + ** Blocking. The sender initiates the process and waits for a response before continuing with the following message
67 + ** Systems depend on the responses of other systems for their function
68 + ** Messages have a time limit. The response needs to be back within 25 seconds (eMagiz default)
69 + ** Uses a request-response structure that talks to one system at a time
70 +* Using the API Gateway pattern can be a valid alternative when dealing with a synchronous integration demand.
71 71  
72 -
73 -
74 74  == 6. Suggested Additional Readings ==
75 75  
76 -If you are interested in this topic, please boost your knowledge with the help of the internet.
74 +If you are interested in this topic and want more information, please read the help text provided by eMagiz.
77 77  
78 78  == 7. Silent demonstration video ==
79 79  
80 -As this is a more theoretical microlearning, we have no video for this.
78 +As this is a more theoretical microlearning, we have no video for this.)))
81 81  
82 -)))
83 -
84 84  ((({{toc/}}))){{/container}}
85 85  {{/container}}