Skip to Content

Changes for page Messaging Asynchronous

Last modified by Danniar Firdausy on 2024/08/21 15:16
From version 5.1
edited by Erik Bakker
on 2023/01/19 19:57
Change comment: There is no comment for this version
To version 2.2
edited by Erik Bakker
on 2022/06/13 11:16
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Messaging Asynchronous
1 +crashcourse-messaging-messaging-asynchronous
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -1,8 +1,13 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 += Messaging Asynchronous =
3 +
2 2  In this microlearning, we will explain the basics of the asynchronous messaging pattern.
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
8 +* Last update: February 25th, 2021
9 +* Required reading time: 5 minutes
10 +
6 6  == 1. Prerequisites ==
7 7  
8 8  * Basic knowledge of the eMagiz platform
... ... @@ -19,9 +19,18 @@
19 19  * Messages can temporarily be kept in the queue if an end system to which the messages need to be delivered is scheduled to go offline
20 20  * Supports one-to-many distribution of messages over the integration landscape
21 21  
27 +
28 +
22 22  == 3. Messaging Asynchronous ==
23 23  
24 24  Asynchronous messaging is the pre-dominant option when you implement a messaging integration via eMagiz.
32 +Key characteristics of asynchronous messaging are:
33 +
34 +* Non-blocking. The sender initiates the process and can continue with the next message
35 +* Systems can therefore be loosely connected
36 +* Messages can temporarily be kept in the queue if an end system to which the messages need to be delivered is scheduled to go offline
37 +* Supports one-to-many distribution of messages over the integration landscape
38 +
25 25  With this method, the sending party supplies the data to eMagiz (via push or pull). eMagiz, in turn, places the data on a queue (in most cases an onramp queue).
26 26  
27 27  This logic means there is no need for the external system to wait for a reply to see what the other system thinks of the message.
... ... @@ -32,6 +32,8 @@
32 32  On top of that, it gives you the option to keep data in a queue temporarily. This functionality is, for example, convenient if there is scheduled maintenance in one of the receiving systems.
33 33  The sending system can continue to send data to eMagiz, and eMagiz will keep it in the queue until the scheduled maintenance is finished.
34 34  
49 +
50 +
35 35  == 4. Assignment ==
36 36  
37 37  Analyze an asynchronous messaging flow from entry to exit and determine which queues are used in the process.
... ... @@ -45,6 +45,8 @@
45 45   * Systems can therefore be loosely connected
46 46   * Messages can temporarily be kept in the queue if an end system to which the messages need to be delivered is scheduled to go offline
47 47  
64 +
65 +
48 48  == 6. Suggested Additional Readings ==
49 49  
50 50  If you are interested in this topic and want more information, please read the help text provided by eMagiz.