Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 21:32
From version 53.1
edited by Erik Bakker
on 2023/01/23 10:21
Change comment: There is no comment for this version
To version 54.1
edited by Eva Torken
on 2023/09/01 15:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.etorken
Content
... ... @@ -39,23 +39,16 @@
39 39  
40 40  The main takeaway should be that adding business logic comes at a price. Depending on the specific requirements, you have to decide whether the pros outweigh the cons. The most crucial part of using business logic is proper documentation. That way, it is clear what the business logic does, why it is there, and how it can be controlled.
41 41  
42 -== 4. Assignment ==
42 +== 4. Key takeaways ==
43 43  
44 -See if you can determine which business logic is implemented in your project and whether that was a wise decision. This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
45 -
46 -== 5. Key takeaways ==
47 -
48 48  * Check out the pros and cons to determine whether business logic in eMagiz makes sense
49 49  * Documentation is key
50 50  
51 -== 6. Suggested Additional Readings ==
47 +== 5. Suggested Additional Readings ==
52 52  
53 53  * [[Asynchronous Routing>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-asynchronous-routing]]
54 54  
51 +)))
55 55  
56 -== 7. Silent demonstration video ==
57 -
58 -There is no video for this microlearning.)))
59 -
60 60  ((({{toc/}}))){{/container}}
61 61  {{/container}}