Skip to Content
Last modified by Danniar Firdausy on 2024/09/16 13:24
From version 37.8
edited by Danniar Firdausy
on 2024/09/16 13:24
Change comment: There is no comment for this version
To version 37.6
edited by Danniar Firdausy
on 2024/09/16 13:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -71,13 +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 - ** Messaging is ideal for low-frequency, low-throughput integrations that don’t require real-time responses.
78 - ** Event streaming excels in handling high-frequency, high-throughput data streams and supports asynchronous communication.
79 - ** API gateway is best suited for synchronous communication and centralized API management with built-in user management and security features.
80 -* Consider licensing, implementation, and resource costs when selecting a pattern, as these factors impact both short-term and long-term investments.
74 +* The key aspects are:
75 + ** The three "first-class" patterns are messaging, event streaming, and API gateway
76 + ** Each pattern has pros and cons
77 + ** Decide which pattern suits best based on business and technical checks and balances
81 81  
82 82  == 5. Suggested Additional Readings ==
83 83