Skip to Content
Last modified by Erik Bakker on 2024/09/03 08:20
From version 8.1
edited by Bouke Reitsma
on 2023/03/03 14:56
Change comment: There is no comment for this version
To version 16.1
edited by Carlijn Kokkeler
on 2024/08/29 11:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.BoukeReitsma
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,6 +1,6 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In this microlearning we'll take a moment to discuss several considerations for making the right choice between the two patterns
3 -
2 +In this guide, we’ll explore key considerations for choosing between eMagiz API Gateway and eMagiz Messaging. Both patterns offer synchronous data handling, but they differ in aspects such as error management, contract requirements, and user management. We'll review these differences to help you decide which pattern best fits your integration needs.
3 +
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
6 6  == 1. Prerequisites ==
... ... @@ -40,19 +40,20 @@
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. Assignment ==
43 +== 4. Key takeaways ==
44 44  
45 -There is no assignment for now in this microlearning
46 -
47 -== 5. Key takeaways ==
48 -
49 49  * There are a set of considerations to make decisions for API gateway vs. messaging
50 50  * Make sure to read the eMagiz Fundamentals properly before taking this section into account in your project
51 51  
52 -== 6. Suggested Additional Readings ==
48 +== 5. Suggested Additional Readings ==
49 +** [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]
50 +*** [[eMagiz API Gateway (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-api-gateway-introduction||target="blank"]]
51 +** [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]
52 +*** [[eMagiz Messaging>>doc:Main.eMagiz Academy.Fundamentals.fundamental-messaging-introduction||target="blank"]]
53 +* [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
54 +** [[Crash Course Messaging (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.WebHome||target="blank"]]
55 +*** [[Introduction (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-introduction||target="blank"]]
56 +** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]]
57 +*** [[Introduction (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-introduction||target="blank"]]
53 53  
54 -Take a moment to read the following [[Usecase>>doc:Main.eMagiz Academy.Use Cases.Pattern Determination.WebHome||target="blank"]]
55 -
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}}
59 +)))((({{toc/}}))){{/container}}{{/container}}