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 3.1
edited by eMagiz
on 2022/06/13 11:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.eMagiz
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -3,6 +3,9 @@
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 +
6 6  == 1. Prerequisites ==
7 7  
8 8  * Basic knowledge of the eMagiz platform
... ... @@ -22,6 +22,13 @@
22 22  == 3. Messaging Asynchronous ==
23 23  
24 24  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 +
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.