Changes for page System vs Multi-tenant System
Last modified by Danniar Firdausy on 2024/09/16 15:04
From version 11.6
edited by Danniar Firdausy
on 2024/09/03 11:11
on 2024/09/03 11:11
Change comment:
There is no comment for this version
To version 11.1
edited by Danniar Firdausy
on 2024/09/03 11:05
on 2024/09/03 11:05
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,7 +1,7 @@ 1 1 {{container}} 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 -In the crashcourse platform, we have focused on the basic concepts to [[Configure a system>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-system||target="blank"]] where you need to drag and drop systems on the canvas within the Capture phase. 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.4 +Within Capture, you need to drag and drop systems on the canvas. In the crashcourse platform, we have focused on the basic concepts to [[Configure a system>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-system||target="blank"]]. 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. 5 5 6 6 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 7 7 ... ... @@ -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 ... ... @@ -48,21 +48,17 @@ 48 48 == 4. Key takeaways == 49 49 50 50 * The key aspects are: 51 -** A system has an individual connection and data exchange with a system 52 -** A multi-tenant system reuses the integration solution but can be deployed differently per tenant 53 -** 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 54 -** In case all communication can run through the eMagiz cloud the API Gateway could be an alternative 55 -** Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous 51 + ** A system has an individual connection and data exchange with a system 52 + ** A multi-tenant system reuses the integration solution but can be deployed differently per tenant 53 + ** 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 54 + ** In case all communication can run through the eMagiz cloud the API Gateway could be an alternative 55 + ** Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous 56 56 57 57 == 5. Suggested Additional Readings == 58 58 59 -If you are interested in this topic and want more information on it please see the following links: 60 - 61 61 * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]] 62 62 ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]] 63 63 *** [[Configure a system (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-system||target="blank"]] 64 -* [[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"]] 65 - 66 66 ))) 67 67 68 68 ((({{toc/}}))){{/container}}