Wiki source code of Messaging Asynchronous
Version 6.1 by Erik Bakker on 2023/01/20 14:30
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | {{container}}{{container layoutStyle="columns"}}((( | ||
2 | In this microlearning, we will explain the basics of the asynchronous messaging pattern. | ||
3 | |||
4 | Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. | ||
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 | |||
35 | == 4. Assignment == | ||
36 | |||
37 | Analyze an asynchronous messaging flow from entry to exit and determine which queues are used in the process. | ||
38 | This assignment can be completed with the help of your (Academy) project you have created/used in the previous assignment. | ||
39 | |||
40 | == 5. Key takeaways == | ||
41 | |||
42 | * Asynchronous messaging is the pre-dominant option when you implement a messaging integration via eMagiz. | ||
43 | * Key characteristics of asynchronous messaging are: | ||
44 | * Non-blocking. The sender initiates the process and can continue with the next message | ||
45 | * Systems can therefore be loosely connected | ||
46 | * 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 | ||
47 | |||
48 | == 6. Suggested Additional Readings == | ||
49 | |||
50 | If you are interested in this topic and want more information, please read the help text provided by eMagiz. | ||
51 | |||
52 | == 7. Silent demonstration video == | ||
53 | |||
54 | This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned. | ||
55 | |||
56 | {{video attachment="crashcourse-messaging-messaging-asynchronous.mp4" reference="Main.Videos.Microlearning.WebHome"/}} | ||
57 | |||
58 | )))((({{toc/}}))){{/container}}{{/container}} |