Last modified by Erik Bakker on 2024/09/05 14:00

From version 18.1
edited by Erik Bakker
on 2023/04/13 14:16
Change comment: There is no comment for this version
To version 22.1
edited by Carlijn Kokkeler
on 2024/09/03 12:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
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.
2 +In this microlearning, we'll explore the best practices for communication between two eMagiz models. Effective communication is crucial, and it's important to prioritize security, loose coupling, maintainability, and clarity. We'll discuss why using queues for inter-model communication is generally discouraged and why alternatives like web services and Event Streaming are preferred. By focusing on these key considerations, you'll be better equipped to design robust and maintainable integration solutions within eMagiz.
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
... ... @@ -34,13 +34,8 @@
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. Assignment ==
37 +== 4. Key takeaways ==
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 -
44 44  * Consider the following when communication between two models
45 45  ** Security
46 46  ** Loose coupling
... ... @@ -47,10 +47,10 @@
47 47  ** Maintainability
48 48  ** Clarity
49 49  
50 -== 6. Suggested Additional Readings ==
45 +== 5. Suggested Additional Readings ==
51 51  
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}}
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 +* [[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"]]
51 +)))((({{toc/}}))){{/container}}{{/container}}