Skip to Content
Last modified by dfirdausy on 2024/09/16 15:04
From version 12.8
edited by dfirdausy
on 2024/09/16 15:03
Change comment: There is no comment for this version
To version 12.10
edited by dfirdausy
on 2024/09/16 15:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -37,9 +37,9 @@
37 37  == 4. Key takeaways ==
38 38  
39 39  * Standard System: Each standard system connects individually and exchanges data with other systems on a case-by-case basis, suitable for scenarios where systems have unique data structures and connectivity requirements.
40 -* Multi-Tenant System: A multi-tenant system allows you to reuse the same integration solution across multiple locations or tenants, standardizing data structures and connectivity, particularly useful for simplifying deployment and management when applications are spread across various locations.
41 -* API Gateway vs. Multi-Tenant Messaging: The API Gateway handles synchronous communication (request and reply), whereas multi-tenant messaging deals with asynchronous data exchange (fire and forget). Choose API Gateway for strict, synchronous requirements and multi-tenant systems for flexible, asynchronous needs.
42 -* Efficiency Considerations: Multi-tenant systems can save time and resources by allowing you to develop a single solution for multiple deployments. The API Gateway enforces stricter rules but can be suitable when all communication can be managed through the eMagiz cloud.
40 +* Multi-Tenant System: A multi-tenant system allows you to reuse the same integration solution across multiple locations or tenants, standardizing data structures and connectivity, ideal for simplifying deployment and management when applications are spread across various locations.
41 +* API Gateway vs. Multi-Tenant Messaging: API Gateway supports synchronous communication, while multi-tenant systems handle asynchronous data exchange.
42 +* Multi-tenant system streamlines deployment and management, whereas the API Gateway is useful for strict, synchronous requirements.
43 43  
44 44  == 5. Suggested Additional Readings ==
45 45