Wiki source code of Messaging Asynchronous
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 | * Last update: February 25th, 2021 | ||
| 7 | * Required reading time: 5 minutes | ||
| 8 | |||
| 9 | == 1. Prerequisites == | ||
| 10 | |||
| 11 | * Basic knowledge of the eMagiz platform | ||
| 12 | |||
| 13 | == 2. Key concepts == | ||
| 14 | |||
| 15 | This microlearning centers around the asynchronous messaging pattern in eMagiz. | ||
| 16 | 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. | ||
| 17 | |||
| 18 | Key characteristics of asynchronous messaging are: | ||
| 19 | |||
| 20 | * Non-blocking. The sender initiates the process and can continue with the following message | ||
| 21 | * Systems can therefore be loosely connected | ||
| 22 | * 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 | ||
| 23 | * Supports one-to-many distribution of messages over the integration landscape | ||
| 24 | |||
| 25 | == 3. Messaging Asynchronous == | ||
| 26 | |||
| 27 | 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 | |||
| 35 | 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). | ||
| 36 | |||
| 37 | 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. | ||
| 38 | 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. | ||
| 39 | |||
| 40 | 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. | ||
| 41 | |||
| 42 | 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. | ||
| 43 | The sending system can continue to send data to eMagiz, and eMagiz will keep it in the queue until the scheduled maintenance is finished. | ||
| 44 | |||
| 45 | == 4. Assignment == | ||
| 46 | |||
| 47 | Analyze an asynchronous messaging flow from entry to exit and determine which queues are used in the process. | ||
| 48 | This assignment can be completed with the help of your (Academy) project you have created/used in the previous assignment. | ||
| 49 | |||
| 50 | == 5. Key takeaways == | ||
| 51 | |||
| 52 | * Asynchronous messaging is the pre-dominant option when you implement a messaging integration via eMagiz. | ||
| 53 | * Key characteristics of asynchronous messaging are: | ||
| 54 | * Non-blocking. The sender initiates the process and can continue with the next message | ||
| 55 | * Systems can therefore be loosely connected | ||
| 56 | * 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 | ||
| 57 | |||
| 58 | == 6. Suggested Additional Readings == | ||
| 59 | |||
| 60 | If you are interested in this topic and want more information, please read the help text provided by eMagiz. | ||
| 61 | |||
| 62 | == 7. Silent demonstration video == | ||
| 63 | |||
| 64 | This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned. | ||
| 65 | |||
| 66 | {{video attachment="crashcourse-messaging-messaging-asynchronous.mp4" reference="Main.Videos.Microlearning.WebHome"/}} | ||
| 67 | |||
| 68 | )))((({{toc/}}))){{/container}}{{/container}} |