Last modified by Danniar Firdausy on 2024/09/18 21:32

From version 55.7
edited by Danniar Firdausy
on 2024/09/18 21:30
Change comment: There is no comment for this version
To version 55.5
edited by Danniar Firdausy
on 2024/09/11 20:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,7 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 -In this microlearning, we will explore how to evaluate the impact of business logic within your integration solution. We will discuss the role of an eMagiz model in managing data exchanges and protocol transformations, and why incorporating complex business rules directly into your eMagiz model may not always be ideal. Instead, we will guide you on where to best place your business logic to ensure efficiency and clarity. Lets dive into making the most of your eMagiz model by balancing business logic and integration goals.
4 +In this microlearning, we will learn what you should consider determining the impact of business logic within your integration solution. An eMagiz model is most useful when exchanging data between systems while taking care of data and protocol transformations. For example, an eMagiz model is generally less suited for incorporating business logic as these rules cannot be defined dynamically and are relatively complex. Filling your eMagiz model with a lot of business logic opens you up for a continuous discussion about data and interpretations of business rules. As that is not the core goal of an eMagiz model, you should always ask yourself what the most suitable place is to incorporate pieces of logic.
5 5  
6 6  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
... ... @@ -12,8 +12,9 @@
12 12  == 2. Key concepts ==
13 13  
14 14  This microlearning centers around considering the impact of business logic
15 -* By business logic, we mean: Rules that determine what should happen to a message
16 16  
16 +By business logic, we mean: Rules that determine what should happen to a message
17 +
17 17  The most interesting point when talking about business logic is:
18 18  
19 19  * Where to draw the line?
... ... @@ -45,8 +45,6 @@
45 45  
46 46  == 5. Suggested Additional Readings ==
47 47  
48 -If you are interested in this topic and want more information, please check out these links:
49 -
50 50  * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
51 51  ** [[Crash Course Messaging (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.WebHome||target="blank"]]
52 52  *** [[Asynchronous Routing (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-asynchronous-routing]]