Skip to Content
Last modified by Waria on 2026/07/23 09:34
From version 12.11
edited by Waria
on 2026/07/23 09:32
Change comment: Renamed back-links.
To version 12.4
edited by dfirdausy
on 2024/09/16 14:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.waria
1 +XWiki.dfirdausy
Content
... ... @@ -17,15 +17,16 @@
17 17  
18 18  == 3. System vs Multi-tenant System ==
19 19  
20 -In this microlearning, we will zoom in on the differences between selecting a 'standard' system and a multi-tenant system to build your integration solution. Knowing the differences between the two is relevant so you can make an informed decision on which option to select when.
20 +In this microlearning, we will zoom in on the differences between selecting a 'standard' system and a multi-tenant system to build your integration solution with. Knowing the differences between the two is relevant so you can make an informed decision on which option to select when.
21 21  
22 -The focal point of this microlearning will be to explain the difference between a 'standard' system and a multi-tenant system. The key aspects are:
22 +The focal point of this microlearning will be to explain the difference between a 'standard' system and a multi-tenant system.
23 23  
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
24 +* The key aspects are:
25 +** A system has an individual connection and data exchange with a system
26 +** A multi-tenant system reuses the integration solution but can be deployed differently per tenant
27 +** 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
28 +** In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
29 +** Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous
29 29  
30 30  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.
31 31  
... ... @@ -37,10 +37,12 @@
37 37  
38 38  == 4. Key takeaways ==
39 39  
40 -* 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.
41 -* 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.
42 -* API Gateway vs. Multi-Tenant Messaging: API Gateway supports synchronous communication, while multi-tenant systems handle asynchronous data exchange.
43 -* Multi-tenant system streamlines deployment and management, whereas the API Gateway is useful for strict, synchronous requirements.
41 +* The key aspects are:
42 +** A system has an individual connection and data exchange with a system
43 +** A multi-tenant system reuses the integration solution but can be deployed differently per tenant
44 +** 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
45 +** In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
46 +** Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous
44 44  
45 45  == 5. Suggested Additional Readings ==
46 46  
... ... @@ -50,12 +50,11 @@
50 50  ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
51 51  *** [[Configure a system (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-system||target="blank"]]
52 52  ** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]]
53 -*** [[Configure Roles and Users (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-user-management||target="blank"]]
56 +*** [[Configure Roles and Users (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-configure-roles-and-users||target="blank"]]
54 54  * [[Multi-tenant system (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22Multi-tenant+system%22||target="blank"]]
55 -)))
56 56  
57 -(((
58 -{{toc/}}
59 59  )))
60 +
61 +((({{toc/}}))){{/container}}
60 60  {{/container}}
61 -{{/container}}
63 +