Skip to Content

Changes for page Messaging Asynchronous

Last modified by Danniar Firdausy on 2024/08/21 15:16
From version 8.3
edited by Danniar Firdausy
on 2024/08/21 15:16
Change comment: There is no comment for this version
To version 7.6
edited by Danniar Firdausy
on 2024/08/20 13:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,7 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In this microlearning, we will explore the basics of the asynchronous messaging pattern within the eMagiz platform. As we delve into this topic, you will gain a clear understanding of how asynchronous communication enables systems to interact efficiently without waiting for immediate responses.
2 +In this microlearning, we will explain the basics of the asynchronous messaging pattern.
3 3  
4 -If you have any questions along the way, feel free to reach out to us at [[academy@emagiz.com>>mailto:academy@emagiz.com]].
4 +Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
6 6  == 1. Prerequisites ==
7 7  
... ... @@ -10,7 +10,7 @@
10 10  == 2. Key concepts ==
11 11  
12 12  This microlearning centers around the asynchronous messaging pattern in eMagiz.
13 -* With asynchronous, we mean: The process that processes data without returning to the sending system with an update on whether the data was processed successfully.
13 +By asynchronous, we mean: The process that processes data without returning to the sending system with an update on whether the data was processed successfully.
14 14  
15 15  Key characteristics of asynchronous messaging are:
16 16  
... ... @@ -36,16 +36,13 @@
36 36  
37 37  * Asynchronous messaging is the pre-dominant option when you implement a messaging integration via eMagiz.
38 38  * Key characteristics of asynchronous messaging are:
39 - ** Non-blocking. This allows the sender to initiate a process and immediately proceed to the next task without waiting for a response.
40 - ** Loose coupling of systems. This ensures that they can operate independently, making it easier to add, replace, or update systems within the integration landscape.
41 - ** Temporary message queuing. 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.
39 + ** Non-blocking. The sender initiates the process and can continue with the next message
40 + ** Systems can therefore be loosely connected
41 + ** 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
42 42  
43 43  == 5. Suggested Additional Readings ==
44 44  
45 45  If you are interested in this topic and want more information on it please see the following links:
46 46  
47 -* [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
48 -** [[Key concepts eMagiz Messaging (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Key concepts eMagiz Messaging.WebHome||target="blank"]]
49 -*** [[Messaging Synchronous (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Key concepts eMagiz Messaging.intermediate-key-concepts-emagiz-messaging-messaging-synchronous.WebHome||target="blank"]]
50 50  * [[Asynchronous Messaging (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22asynchronous+messaging%22||target="blank"]]
51 51  )))((({{toc/}}))){{/container}}{{/container}}