Skip to Content

Changes for page Messaging Asynchronous

Last modified by Danniar Firdausy on 2024/08/21 15:16
From version 1.1
edited by eMagiz
on 2022/05/10 11:12
Change comment: There is no comment for this version
To version 5.1
edited by Erik Bakker
on 2023/01/19 19:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +Messaging Asynchronous
Parent
... ... @@ -1,0 +1,1 @@
1 +WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.marijn
1 +XWiki.ebakker
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -1,20 +1,8 @@
1 -{{html wiki="true"}}
2 -<div class="ez-academy">
3 - <div class="ez-academy_body">
4 -
5 -<div class="doc">
6 -
7 -
8 -
9 -= Messaging Asynchronous =
10 -
1 +{{container}}{{container layoutStyle="columns"}}(((
11 11  In this microlearning, we will explain the basics of the asynchronous messaging pattern.
12 12  
13 -Should you have any questions, please get in touch with academy@emagiz.com.
4 +Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
14 14  
15 -* Last update: February 25th, 2021
16 -* Required reading time: 5 minutes
17 -
18 18  == 1. Prerequisites ==
19 19  
20 20  * Basic knowledge of the eMagiz platform
... ... @@ -31,18 +31,9 @@
31 31  * 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
32 32  * Supports one-to-many distribution of messages over the integration landscape
33 33  
34 -
35 -
36 36  == 3. Messaging Asynchronous ==
37 37  
38 38  Asynchronous messaging is the pre-dominant option when you implement a messaging integration via eMagiz.
39 -Key characteristics of asynchronous messaging are:
40 -
41 -* Non-blocking. The sender initiates the process and can continue with the next message
42 -* Systems can therefore be loosely connected
43 -* 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 -* Supports one-to-many distribution of messages over the integration landscape
45 -
46 46  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).
47 47  
48 48  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.
... ... @@ -53,8 +53,6 @@
53 53  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.
54 54  The sending system can continue to send data to eMagiz, and eMagiz will keep it in the queue until the scheduled maintenance is finished.
55 55  
56 -===== Practice =====
57 -
58 58  == 4. Assignment ==
59 59  
60 60  Analyze an asynchronous messaging flow from entry to exit and determine which queues are used in the process.
... ... @@ -68,8 +68,6 @@
68 68   * Systems can therefore be loosely connected
69 69   * 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
70 70  
71 -
72 -
73 73  == 6. Suggested Additional Readings ==
74 74  
75 75  If you are interested in this topic and want more information, please read the help text provided by eMagiz.
... ... @@ -78,10 +78,6 @@
78 78  
79 79  This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
80 80  
81 -<iframe width="1280" height="720" src="../../vid/microlearning/crashcourse-messaging-messaging-asynchronous.mp4" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
56 +{{video attachment="crashcourse-messaging-messaging-asynchronous.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
82 82  
83 -</div>
84 -</div>
85 -</div>
86 -
87 -{{/html}}
58 +)))((({{toc/}}))){{/container}}{{/container}}