Wiki source code of Messaging Asynchronous
Version 7.2 by Danniar Firdausy on 2024/08/20 12:51
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
2.1 | 1 | {{container}}{{container layoutStyle="columns"}}((( |
| |
1.1 | 2 | In this microlearning, we will explain the basics of the asynchronous messaging pattern. |
| 3 | |||
| |
2.1 | 4 | Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. |
| |
1.1 | 5 | |
| 6 | == 1. Prerequisites == | ||
| 7 | |||
| 8 | * Basic knowledge of the eMagiz platform | ||
| 9 | |||
| 10 | == 2. Key concepts == | ||
| 11 | |||
| 12 | This microlearning centers around the asynchronous messaging pattern in eMagiz. | ||
| 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 | |||
| 15 | Key characteristics of asynchronous messaging are: | ||
| 16 | |||
| 17 | * Non-blocking. The sender initiates the process and can continue with the following message | ||
| 18 | * Systems can therefore be loosely connected | ||
| 19 | * 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 | ||
| 20 | * Supports one-to-many distribution of messages over the integration landscape | ||
| 21 | |||
| 22 | == 3. Messaging Asynchronous == | ||
| 23 | |||
| 24 | Asynchronous messaging is the pre-dominant option when you implement a messaging integration via eMagiz. | ||
| 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 | |||
| 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. | ||
| 28 | Furthermore, the system can supply the data somewhere and forget about it. eMagiz will ensure to deliver the information to all systems that want to receive the data. | ||
| 29 | |||
| 30 | Because of this loose coupling between systems via the asynchronous five-layer model in eMagiz, you can add supplying and receiving systems quickly and replace them if necessary. | ||
| 31 | |||
| 32 | 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. | ||
| 33 | The sending system can continue to send data to eMagiz, and eMagiz will keep it in the queue until the scheduled maintenance is finished. | ||
| 34 | |||
| |
7.2 | 35 | == 4. Key takeaways == |
| |
1.1 | 36 | |
| 37 | * Asynchronous messaging is the pre-dominant option when you implement a messaging integration via eMagiz. | ||
| 38 | * Key characteristics of asynchronous messaging are: | ||
| |
7.1 | 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 | ||
| |
1.1 | 42 | |
| |
7.2 | 43 | == 5. Suggested Additional Readings == |
| |
1.1 | 44 | |
| 45 | If you are interested in this topic and want more information, please read the help text provided by eMagiz. | ||
| 46 | |||
| |
2.1 | 47 | )))((({{toc/}}))){{/container}}{{/container}} |