Skip to Content
Last modified by Danniar Firdausy on 2024/09/16 15:04
From version 11.5
edited by Danniar Firdausy
on 2024/09/03 11:09
Change comment: There is no comment for this version
To version 11.6
edited by Danniar Firdausy
on 2024/09/03 11:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,11 +18,11 @@
18 18  The focal point of this microlearning will be to explain the difference between a 'standard' system and a multi-tenant system.
19 19  
20 20  * The key aspects are:
21 - ** A system has an individual connection and data exchange with a system
22 - ** A multi-tenant system reuses the integration solution but can be deployed differently per tenant
23 - ** 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
24 - ** In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
25 - ** Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous
21 +** A system has an individual connection and data exchange with a system
22 +** A multi-tenant system reuses the integration solution but can be deployed differently per tenant
23 +** 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
24 +** In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
25 +** Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous
26 26  
27 27  == 3. System vs Multi-tenant System ==
28 28  
... ... @@ -31,11 +31,11 @@
31 31  The focal point of this microlearning will be to explain the difference between a 'standard' system and a multi-tenant system.
32 32  
33 33  * The key aspects are:
34 - ** A system has an individual connection and data exchange with a system
35 - ** A multi-tenant system reuses the integration solution but can be deployed differently per tenant
36 - ** 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
37 - ** In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
38 - ** Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous
34 +** A system has an individual connection and data exchange with a system
35 +** A multi-tenant system reuses the integration solution but can be deployed differently per tenant
36 +** 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
37 +** In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
38 +** Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous
39 39  
40 40  As stated above when summarizing the key aspects of the choice we first need to look at how we look at the world when creating the integration data model. Do we adhere to the structure as dictated by each system with whom we want to connect? If so we should always opt for the standard system in Capture as each of those systems will also vary in the data structure, connectivity, and authentication.
41 41