Skip to Content
Last modified by Danniar Firdausy on 2024/09/16 15:04
From version 4.1
edited by Erik Bakker
on 2022/08/25 11:36
Change comment: There is no comment for this version
To version 3.1
edited by eMagiz
on 2022/06/09 11:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.eMagiz
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -5,6 +5,9 @@
5 5  
6 6  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
8 +* Last update: July 28th, 2021
9 +* Required reading time: 5 minutes
10 +
8 8  == 1. Prerequisites ==
9 9  
10 10  * Basic knowledge of the eMagiz platform
... ... @@ -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
24 + * A system has an individual connection and data exchange with a system
25 + * A multi-tenant system reuses the integration solution but can be deployed differently per tenant
26 + * 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
27 + * In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
28 + * Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous
26 26  
27 27  
28 28  
... ... @@ -33,11 +33,11 @@
33 33  The focal point of this microlearning will be to explain the difference between a 'standard' system and a multi-tenant system.
34 34  
35 35  * The key aspects are:
36 - ** A system has an individual connection and data exchange with a system
37 - ** A multi-tenant system reuses the integration solution but can be deployed differently per tenant
38 - ** 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
39 - ** In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
40 - ** Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous
39 + * A system has an individual connection and data exchange with a system
40 + * A multi-tenant system reuses the integration solution but can be deployed differently per tenant
41 + * 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
42 + * In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
43 + * Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous
41 41  
42 42  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.
43 43  
... ... @@ -54,12 +54,14 @@
54 54  == 5. Key takeaways ==
55 55  
56 56  * The key aspects are:
57 - ** A system has an individual connection and data exchange with a system
58 - ** A multi-tenant system reuses the integration solution but can be deployed differently per tenant
59 - ** 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
60 - ** In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
61 - ** Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous
60 + * A system has an individual connection and data exchange with a system
61 + * A multi-tenant system reuses the integration solution but can be deployed differently per tenant
62 + * 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
63 + * In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
64 + * Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous
62 62  
66 +
67 +
63 63  == 6. Suggested Additional Readings ==
64 64  
65 65  If you are interested in this topic and want more information on it please read the help texts provided by eMagiz