Messaging Asynchronous

{{container}}{{container layoutStyle="columns"}}(((

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.

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]].

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

* 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.

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. Key takeaways ==

36

37

* Asynchronous messaging is the pre-dominant option when you implement a messaging integration via eMagiz.

38

* Key characteristics of asynchronous messaging are:

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

43

== 5. Suggested Additional Readings ==

44

45

If you are interested in this topic and want more information on it please see the following links:

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

* [[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

)))((({{toc/}}))){{/container}}{{/container}}

Wiki source code of Messaging Asynchronous

Navigation