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 1.2
edited by eMagiz
on 2022/06/08 14:45
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 - System vs Multi-tenant System
1 +intermediate-solution-architecture-system-vs-multi-tenant-system
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.marijn
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -1,10 +1,20 @@
1 -{{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
1 +{{html wiki="true"}}
2 +<div class="ez-academy">
3 + <div class="ez-academy_body">
4 +
5 +<div class="doc">
6 +
7 +
8 +
9 += System vs Multi-tenant System =
10 +
4 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](crashcourse-platform-capture-configure-a-system.md). 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 -Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
13 +Should you have any questions, please contact academy@emagiz.com.
7 7  
15 +* Last update: July 28th, 2021
16 +* Required reading time: 5 minutes
17 +
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
31 + * A system has an individual connection and data exchange with a system
32 + * A multi-tenant system reuses the integration solution but can be deployed differently per tenant
33 + * 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
34 + * In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
35 + * 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
46 + * A system has an individual connection and data exchange with a system
47 + * A multi-tenant system reuses the integration solution but can be deployed differently per tenant
48 + * 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
49 + * In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
50 + * 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  
... ... @@ -47,6 +47,8 @@
47 47  
48 48  Based on the above considerations you should be able to determine which solution fits your integration challenge.
49 49  
60 +===== Practice =====
61 +
50 50  == 4. Assignment ==
51 51  
52 52  Reflect on the choices made within various projects and see if you would, with what you know now, change the specific implementation.
... ... @@ -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
69 + * A system has an individual connection and data exchange with a system
70 + * A multi-tenant system reuses the integration solution but can be deployed differently per tenant
71 + * 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
72 + * In case all communication can run through the eMagiz cloud the API Gateway could be an alternative
73 + * Choosing between API Gateway and multi-tenant in messaging is a question on synchronous vs asynchronous
62 62  
75 +
76 +
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
... ... @@ -67,8 +67,10 @@
67 67  == 7. Silent demonstration video ==
68 68  
69 69  As this is a more theoretical microlearning we have no video for this
70 -)))
71 71  
72 -((({{toc/}}))){{/container}}
73 -{{/container}}
85 +</div>
74 74  
87 +</div>
88 +</div>
89 +
90 +{{/html}}