Changes for page Messaging Synchronous

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -30,12 +30,12 @@
30	30
31	31	Key characteristics of synchronous messaging are:
32	32
33		-- Blocking. The sender initiates the process and waits for a response before continuing with the following message
34		-- Systems depend on the responses of other systems for their function
35		-- Messages have a time limit. The response needs to be back within 25 seconds (eMagiz default)
36		-- Uses a request-response structure that talks to one system at a time
	33	+* Blocking. The sender initiates the process and waits for a response before continuing with the following message
	34	+* Systems depend on the responses of other systems for their function
	35	+* Messages have a time limit. The response needs to be back within 25 seconds (eMagiz default)
	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"]]
	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"]].
39	39
40	40	[[image:Main.Images.Microlearning.WebHome@intermediate-key-concepts-emagiz-messaging-messaging-synchronous--concept.png]]
41	41
...	...	@@ -45,29 +45,40 @@
45	45
46	46	A third aspect to consider is whether you can set a generic point of entry through which all clients can communicate via eMagiz to many other systems. In those cases, you could look at the API Gateway solution as an alternative to synchronous messaging, as it comes with several benefits. More on the basics of the API Gateway can be found in this [[crashcourse>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]].
47	47
48		-== 4. Assignment ==
	48	+=== 3.1 Practical use case ===
49	49
50		-No assignment accompanies this microlearning.
	50	+A practical use case in which you would most likely want to handle your integration synchronously is the following use case:
51	51
52		-== 5. Key takeaways ==
	52	+Imagine you want to order something at a webshop. After you have selected the product(s), you want to open the payment process to pay. Upon payment, you also need to supply the relevant address information, so the webshop knows where to deliver the product. In doing so, you often see that when you provide your postal code (and house number), the system will automatically fill in the remainder of your address information. This functionality is there for two reasons. Your convenience and because the webshop needs this information to deliver the product you paid for correctly. If the webshop does not know where to deliver the product, the webshop cannot complete the order process. As a result, the webshop needs to send out a request that will promptly be followed by a response (a synchronous call).
53	53
54		-* The key aspects are:
55		- * Entry is the starting point of the integration process in messaging
56		- * Queues are an internal resource of eMagiz
57		- * Outside parties are not allowed to write on eMagiz queues directly
58		- * eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
	54	+Even in this scenario, most web shops give the user the option to manually fill in the remainder of the information as they know that even when the call fails, the user still needs a way to continue. So in a sense, the webshop has taken the responsibility of handling success and failure responses.
59	59
	56	+=== 3.2 Asynchronous vs Synchronous ===
60	60
	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)
61	61
	60	+== 4. Assignment ==
	61	+
	62	+Analyze a synchronous messaging flow from entry to exit and learn what happens within this process.
	63	+This assignment can be completed with the help of your (Academy) project you have created/used in the previous assignment.
	64	+
	65	+== 5. Key takeaways ==
	66	+
	67	+* Synchronous messaging is the less used, the less advised option when implementing a messaging integration via eMagiz
	68	+* Key characteristics of synchronous messaging are:
	69	+ ** Blocking. The sender initiates the process and waits for a response before continuing with the following message
	70	+ ** Systems depend on the responses of other systems for their function
	71	+ ** Messages have a time limit. The response needs to be back within 25 seconds (eMagiz default)
	72	+ ** Uses a request-response structure that talks to one system at a time
	73	+* Using the API Gateway pattern can be a valid alternative when dealing with a synchronous integration demand.
	74	+
62	62	== 6. Suggested Additional Readings ==
63	63
64		-If you are interested in this topic, please boost your knowledge with the help of the internet.
	77	+If you are interested in this topic and want more information, please read the help text provided by eMagiz.
65	65
66	66	== 7. Silent demonstration video ==
67	67
68		-As this is a more theoretical microlearning, we have no video for this.
	81	+As this is a more theoretical microlearning, we have no video for this.)))
69	69
70		-)))
71		-
72	72	((({{toc/}}))){{/container}}
73	73	{{/container}}