Skip to Content

Changes for page Messaging Asynchronous

Last modified by Danniar Firdausy on 2024/08/21 15:16
From version 3.1
edited by eMagiz
on 2022/06/13 11:26
Change comment: There is no comment for this version
To version 7.1
edited by Erik Bakker
on 2023/01/20 14:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -3,9 +3,6 @@
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
6 -* Last update: February 25th, 2021
7 -* Required reading time: 5 minutes
8 -
9 9  == 1. Prerequisites ==
10 10  
11 11  * Basic knowledge of the eMagiz platform
... ... @@ -25,13 +25,6 @@
25 25  == 3. Messaging Asynchronous ==
26 26  
27 27  Asynchronous messaging is the pre-dominant option when you implement a messaging integration via eMagiz.
28 -Key characteristics of asynchronous messaging are:
29 -
30 -* Non-blocking. The sender initiates the process and can continue with the next message
31 -* Systems can therefore be loosely connected
32 -* 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
33 -* Supports one-to-many distribution of messages over the integration landscape
34 -
35 35  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).
36 36  
37 37  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.
... ... @@ -51,9 +51,9 @@
51 51  
52 52  * Asynchronous messaging is the pre-dominant option when you implement a messaging integration via eMagiz.
53 53  * Key characteristics of asynchronous messaging are:
54 - * Non-blocking. The sender initiates the process and can continue with the next message
55 - * Systems can therefore be loosely connected
56 - * 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
44 + ** Non-blocking. The sender initiates the process and can continue with the next message
45 + ** Systems can therefore be loosely connected
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
57 57  
58 58  == 6. Suggested Additional Readings ==
59 59