Skip to Content

Changes for page Messaging Synchronous

Last modified by Danniar Firdausy on 2024/09/16 13:37
From version 13.10
edited by Danniar Firdausy
on 2024/09/16 13:30
Change comment: There is no comment for this version
To version 13.11
edited by Danniar Firdausy
on 2024/09/16 13:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,7 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 -In this microlearning, we will explain the basics of the synchronous messaging pattern.
4 +In this microlearning session, we will introduce you to the basics of the synchronous messaging pattern within the eMagiz platform. You will gain an understanding of how this pattern operates, its key characteristics, and when it may or may not be the best choice for your integrations.
5 5  
6 6  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
... ... @@ -67,13 +67,12 @@
67 67  
68 68  == 4. Key takeaways ==
69 69  
70 -* Synchronous messaging is the less used, the less advised option when implementing a messaging integration via eMagiz
71 -* Key characteristics of synchronous messaging are:
72 - ** Blocking. The sender initiates the process and waits for a response before continuing with the following message
73 - ** Systems depend on the responses of other systems for their function
74 - ** Messages have a time limit. The response needs to be back within 25 seconds (eMagiz default)
75 - ** Uses a request-response structure that talks to one system at a time
76 -* Using the API Gateway pattern can be a valid alternative when dealing with a synchronous integration demand.
70 +* Key characteristics of synchronous messaging include:
71 +** Blocking: The sender must wait for a response before proceeding with the next message.
72 +** System dependency: Systems rely on timely responses from others to function effectively.
73 +** Time constraints: Messages have a time limit (25 seconds by default in eMagiz) for receiving a response.
74 +** Request-response structure: Each request is handled by one system at a time.
75 +* The API Gateway pattern is often a better alternative when handling synchronous communication, as it offers more flexibility and mitigates some of the challenges associated with synchronous messaging.
77 77  
78 78  == 5. Suggested Additional Readings ==
79 79