Skip to Content
Last modified by Danniar Firdausy on 2024/09/16 13:24
From version 37.7
edited by Danniar Firdausy
on 2024/09/16 13:23
Change comment: There is no comment for this version
To version 37.5
edited by Danniar Firdausy
on 2024/09/16 13:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -20,6 +20,15 @@
20 20  
21 21  == 3. Determining Integration Pattern ==
22 22  
23 +In eMagiz, we differentiate between three "first-class" integration patterns. Each of these patterns is best suited for particular integration challenges. In this microlearning, we will see how to compare the three integration patterns to decide which pattern to choose.
24 +
25 +The focal point of this microlearning will be to figure out how you can best decide between the various "first-class" integration patterns.
26 +
27 +* The key aspects are:
28 + ** The three "first-class" patterns are messaging, event streaming, and API gateway
29 + ** Each pattern has pros and cons
30 + ** Decide which pattern suits best based on business and technical checks and balances
31 +
23 23  As stated above, there are three "first-class" integration patterns within eMagiz. Each of these patterns has a unique way of processing the data. In this microlearning, we will look at how to decide which pattern best fits your integration challenge. Before we do that, let us first quickly look at the three integration patterns. In the picture below, you see a visual representation of each of the three patterns.
24 24  
25 25  [[image:Main.Images.Microlearning.WebHome@intermediate-discover-your-integration-landscape-determining-integration-pattern--the-three-patterns-visualized.png]]
... ... @@ -71,14 +71,10 @@
71 71  
72 72  == 4. Key takeaways ==
73 73  
74 -* eMagiz offers three "first-class" integration patterns: messaging, event streaming, and API gateway.
75 -* Each pattern is designed to address specific integration scenarios, with distinct strengths and limitations.
76 -* Choosing the right pattern depends on a combination of business requirements (e.g., real-time response needs, data retention, throughput) and technical considerations (e.g., system compatibility, security protocols).
77 -* In general:
78 - ** Messaging is ideal for low-frequency, low-throughput integrations that don’t require real-time responses.
79 - ** Event streaming excels in handling high-frequency, high-throughput data streams and supports asynchronous communication.
80 - ** API gateway is best suited for synchronous communication and centralized API management with built-in user management and security features.
81 -* Consider licensing, implementation, and resource costs when selecting a pattern, as these factors impact both short-term and long-term investments.
83 +* The key aspects are:
84 + ** The three "first-class" patterns are messaging, event streaming, and API gateway
85 + ** Each pattern has pros and cons
86 + ** Decide which pattern suits best based on business and technical checks and balances
82 82  
83 83  == 5. Suggested Additional Readings ==
84 84