Skip to Content
Last modified by Erik Bakker on 2024/09/03 08:20
From version 10.1
edited by Danniar Firdausy
on 2023/10/09 08:32
Change comment: There is no comment for this version
To version 8.1
edited by Bouke Reitsma
on 2023/03/03 14:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.BoukeReitsma
Content
... ... @@ -40,13 +40,19 @@
40 40   ** API gateway offers a easy to configure user management capability to protect operations. Users and roles can be designed in the Design phase, and various authentication methods are allowed such as OAuth2.0 and API Keys. eMagiz offers easy to use configurations for that
41 41   ** For Messaging, no such user management options exit and all needs to be created inside the flows that handle the requests & replies.
42 42  
43 -== 4. Key takeaways ==
43 +== 4. Assignment ==
44 44  
45 +There is no assignment for now in this microlearning
46 +
47 +== 5. Key takeaways ==
48 +
45 45  * There are a set of considerations to make decisions for API gateway vs. messaging
46 46  * Make sure to read the eMagiz Fundamentals properly before taking this section into account in your project
47 47  
48 -== 5. Suggested Additional Readings ==
52 +== 6. Suggested Additional Readings ==
49 49  
50 50  Take a moment to read the following [[Usecase>>doc:Main.eMagiz Academy.Use Cases.Pattern Determination.WebHome||target="blank"]]
51 51  
52 -)))((({{toc/}}))){{/container}}{{/container}}
56 +== 7. Silent demonstration video ==
57 +
58 +As this is a more theoretical microlearning, we have no video that accompanies this microlearning.)))((({{toc/}}))){{/container}}{{/container}}