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

Summary

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 +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 dive into the key differences between 'standard' systems and multi-tenant systems within the eMagiz platform. Understanding these differences is crucial for selecting the right option for your integration solution. We will cover how each system type impacts configuration, deployment, and communication to help you make an informed decision.
5 5  
6 6  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
... ... @@ -13,30 +13,19 @@
13 13  
14 14  This microlearning centers on a 'standard' system vs a multi-tenant system.
15 15  
16 -With a multi-tenant system we mean: A system that can be deployed in various locations but uses the same functionality across those locations
16 +* With a multi-tenant system we mean: A system that can be deployed in various locations but uses the same functionality across those locations.
17 17  
18 -The focal point of this microlearning will be to explain the difference between a 'standard' system and a multi-tenant system.
19 -
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
26 -
27 27  == 3. System vs Multi-tenant System ==
28 28  
29 -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.
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.
30 30  
31 -The focal point of this microlearning will be to explain the difference between a 'standard' system and a multi-tenant system.
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:
23 +* A system has an individual connection and data exchange with a system
24 +* A multi-tenant system reuses the integration solution but can be deployed differently per tenant
25 +* 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
26 +* In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
27 +* Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous
32 32  
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
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  
42 42  However, when we turn our viewpoint from inside out to outside in and determine that for some structures (i.e., Order entry process) it would be very handy to define a standard set of rules in terms of the data structure, connectivity, and authentication using a multi-tenant system could be very beneficial. This way you can build a solution once and deploy it many. With that construction, you can significantly save time while developing and while managing the solution.
... ... @@ -47,16 +47,14 @@
47 47  
48 48  == 4. Key takeaways ==
49 49  
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
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.
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:
46 +If you are interested in this topic and want more information on it please read the help text provided by eMagiz and read the following links:
60 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"]]