Skip to Content

Changes for page Messaging Asynchronous

Last modified by Danniar Firdausy on 2024/08/21 15:16
From version 4.1
edited by Erik Bakker
on 2022/08/11 16:10
Change comment: There is no comment for this version
To version 6.1
edited by Erik Bakker
on 2023/01/20 14:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -22,13 +22,6 @@
22 22  == 3. Messaging Asynchronous ==
23 23  
24 24  Asynchronous messaging is the pre-dominant option when you implement a messaging integration via eMagiz.
25 -Key characteristics of asynchronous messaging are:
26 -
27 -* Non-blocking. The sender initiates the process and can continue with the next message
28 -* Systems can therefore be loosely connected
29 -* 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
30 -* Supports one-to-many distribution of messages over the integration landscape
31 -
32 32  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).
33 33  
34 34  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.