Changes for page Communication between models
Last modified by Erik Bakker on 2024/09/05 14:00
From version 25.1
edited by Erik Bakker
on 2024/09/05 14:00
on 2024/09/05 14:00
Change comment:
There is no comment for this version
To version 18.1
edited by Erik Bakker
on 2023/04/13 14:16
on 2023/04/13 14:16
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,5 +1,5 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 - In this microlearning,we'll explorethebest practicesforcommunication betweentwoeMagizmodels. Effectivecommunicationiscrucial,and it'smportanttoprioritizeecurity, loosecoupling,maintainability,and clarity.We'lldiscusswhyusingqueuesforinter-modelcommunicationisgenerallydiscouragedandwhy alternativeslikeweb servicesand EventStreamingarepreferred. By focusingon thesekeyconsiderations,you'll be better equippedtodesignrobustandmaintainableintegrationsolutionswithineMagiz.2 +When your integration landscape grows through time, you might decide to split functional business processes into multiple eMagiz models. In those cases, the question of connecting these models easily, stable, and securely could arise. This microlearning will focus on that question and provide an answer based on our vision and best practices when dealing with the platform. 3 3 4 4 Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 5 5 ... ... @@ -34,8 +34,13 @@ 34 34 35 35 Both alternatives have the benefit that the security can be tight and explicit (i.e., only model A can write/post data to model B). Furthermore, managing the solution becomes much easier as it uses the standard functionality within the platform. Therefore, we have no plans to support this approach in the product. 36 36 37 -== 4. Keytakeaways==37 +== 4. Assignment == 38 38 39 +Consider what your criteria are when communicating between models and compare them to our criteria. 40 +This assignment can be completed with the help of the (Academy) project you created/used in the previous assignment. 41 + 42 +== 5. Key takeaways == 43 + 39 39 * Consider the following when communication between two models 40 40 ** Security 41 41 ** Loose coupling ... ... @@ -42,14 +42,10 @@ 42 42 ** Maintainability 43 43 ** Clarity 44 44 45 -== 5. Suggested Additional Readings ==50 +== 6. Suggested Additional Readings == 46 46 47 -* [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]] 48 -** [[eMagiz Security Guide (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-security-guide||target="blank"]] 49 -** [[Multi-Model Explained (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-multi-model-explained.WebHome||target="blank"]] 50 -** [[Multi-Model Best Practice (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-multi-model-best-practice.WebHome||target="blank"]] 51 -* [[Advanced (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.WebHome||target="blank"]] 52 -** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.WebHome||target="blank"]] 53 -*** [[Checklist for Splitting Models (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.Checklist for Splitting Models.WebHome||target="blank"]] 54 -* [[Communication between models (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=communication+between+models||target="blank"]] 55 -)))((({{toc/}}))){{/container}}{{/container}} 52 +If you are interested in this topic and want more information, please consult us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] 53 + 54 +== 7. Silent demonstration video == 55 + 56 +As this is more of theoretical microlearning, there is no video accompanying the microlearning.)))((({{toc/}}))){{/container}}{{/container}}