Skip to Content
Last modified by Danniar Firdausy on 2024/09/16 15:04
From version 12.6
edited by Danniar Firdausy
on 2024/09/16 15:01
Change comment: There is no comment for this version
To version 12.9
edited by Danniar Firdausy
on 2024/09/16 15:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -36,12 +36,10 @@
36 36  
37 37  == 4. Key takeaways ==
38 38  
39 -* The key aspects are:
40 -** A system has an individual connection and data exchange with a system
41 -** A multi-tenant system reuses the integration solution but can be deployed differently per tenant
42 -** Multi-tenant solution is handy in case you want to standardize but the supplying (or receiving) applications are deployed on varying locations instead of a single location
43 -** In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
44 -** Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous
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, 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.
45 45  
46 46  == 5. Suggested Additional Readings ==
47 47