Skip to Content
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
Change comment: There is no comment for this version
To version 11.7
edited by Danniar Firdausy
on 2024/09/03 11:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -39,9 +39,9 @@
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.
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.
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 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.
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.
45 45  
46 46  Based on the above considerations you should be able to determine which solution fits your integration challenge.
47 47  
... ... @@ -61,6 +61,8 @@
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 +** [[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"]]
64 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 65  
66 66  )))