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 7.1
edited by Erik Bakker
on 2023/01/23 08:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -System vs Multi-tenant System
1 + System vs Multi-tenant System
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
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,53 +18,55 @@
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 +
28 +
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.
31 +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.WebHome||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.
30 30  
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
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 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 -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.
44 +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.
43 43  
44 -But then what about the API Gateway? Does that not also define a standard set of rules in terms of the data structure, connectivity, and authentication. Yes, it does. There are however two key differences when choosing between the API Gateway solution and a multi-tenant messaging system. The first key difference lies in synchronicity. The API Gateway deals with synchronous traffic (i.e., request and reply structure) whereas the multi-tenant option would handle data asynchronously (i.e., fire and forget). The second key difference lies in the strictness of the pattern. If you want to implement the API Gateway you need to adhere to a stricter set of rules as most in eMagiz is autogenerated for you. The same does not apply to messaging in that regard as you would typically start with an empty canvas and are relatively free to do with it what you see fit.
46 +But then what about the API Gateway? Does that not also define a standard set of rules in terms of the data structure, connectivity, and authentication. Yes, it does. There are however two key differences when choosing between the API Gateway solution and a multi-tenant messaging system. The first key difference lies in synchronicity. The API Gateway deals with synchronous traffic (i.e. request and reply structures) whereas the multi-tenant option would handle data asynchronously (i.e. fire and forget). The second key difference lies in the strictness of the pattern. If you want to implement the API Gateway you need to adhere to a stricter set of rules as most in eMagiz is autogenerated for you. The same does not apply to messaging in that regard as you would typically start with an empty canvas and are relatively free to do with it what you see fit.
45 45  
46 46  Based on the above considerations you should be able to determine which solution fits your integration challenge.
47 47  
48 -== 4. Key takeaways ==
50 +== 4. Assignment ==
49 49  
52 +Reflect on the choices made within various projects and see if you would, with what you know now, change the specific implementation.
53 +
54 +== 5. Key takeaways ==
55 +
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
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
56 56  
57 -== 5. Suggested Additional Readings ==
63 +== 6. Suggested Additional Readings ==
58 58  
59 -If you are interested in this topic and want more information on it please see the following links:
65 +If you are interested in this topic and want more information on it please read the help texts provided by eMagiz
60 60  
61 -* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
62 -** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
63 -*** [[Configure a system (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-system||target="blank"]]
64 -** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]]
65 -*** [[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"]]
66 -* [[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"]]
67 +== 7. Silent demonstration video ==
67 67  
69 +As this is a more theoretical microlearning we have no video for this
68 68  )))
69 69  
70 70  ((({{toc/}}))){{/container}}