Skip to Content
Last modified by Danniar Firdausy on 2024/09/16 15:04
From version 12.5
edited by Danniar Firdausy
on 2024/09/16 15:00
Change comment: There is no comment for this version
To version 12.6
edited by Danniar Firdausy
on 2024/09/16 15:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -19,15 +19,13 @@
19 19  
20 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.
21 21  
22 -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
23 23  
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
30 -
31 31  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.
32 32  
33 33  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.