Skip to Content
Last modified by Erik Bakker on 2024/09/03 08:20
From version 4.1
edited by Erik Bakker
on 2022/06/13 10:07
Change comment: There is no comment for this version
To version 12.2
edited by Danniar Firdausy
on 2024/08/20 13:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -3,9 +3,6 @@
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
6 -* Last update: December 2021
7 -* Required reading time: 10 minutes
8 -
9 9  == 1. Prerequisites ==
10 10  
11 11  * Advanced knowledge of the eMagiz platform
... ... @@ -16,8 +16,8 @@
16 16  
17 17  Please refer to the following Fundamentals to learn the key concepts of both patterns
18 18  
19 -* [[eMagiz API Gateway>>doc:Main.eMagiz Academy.Fundamentals.fundamental-api-gateway-introduction.WebHome||target="blank"]]
20 -* [[eMagiz Messaging>>doc:Main.eMagiz Academy.Fundamentals.fundamental-messaging-introduction.WebHome||target="blank"]]
16 +* [[eMagiz API Gateway>>doc:Main.eMagiz Academy.Fundamentals.fundamental-api-gateway-introduction||target="blank"]]
17 +* [[eMagiz Messaging>>doc:Main.eMagiz Academy.Fundamentals.fundamental-messaging-introduction||target="blank"]]
21 21  
22 22  == 3. Considerations for API Gateway or Messaging ==
23 23  
... ... @@ -37,25 +37,24 @@
37 37   ** Messaging required a fixed contract between the message definitions that are exchanged. A change of definition would result in validation issues and therefore more communication is required
38 38   ** For an API Gateway solution, the contract is published via the API Gateway outwards. The basic idea is that the data definition is fixed and standardized, and that requesting application will adapt their request to this definition. In that sense the API Gateway offers standardization in the landscape
39 39  * **Technical disqualifiers**
40 - ** For an API Gateway, the requestor needs to be able to call a REST based webservice using JSON formatted messages.
37 + ** For an API Gateway, the requestor needs to be able to call a REST based webservice using a supported messaging format
41 41   ** Messaging allows other web services such as SOAP, but can also handle XML for instance
42 42  * **Centralized User Management**
43 43   ** 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
44 44   ** For Messaging, no such user management options exit and all needs to be created inside the flows that handle the requests & replies.
45 45  
46 -== 4. Assignment ==
43 +== 4. Key takeaways ==
47 47  
48 -There is no assignment for now in this microlearning
49 -
50 -== 5. Key takeaways ==
51 -
52 52  * There are a set of considerations to make decisions for API gateway vs. messaging
53 53  * Make sure to read the eMagiz Fundamentals properly before taking this section into account in your project
54 54  
55 -== 6. Suggested Additional Readings ==
48 +== 5. Suggested Additional Readings ==
56 56  
57 -Take a moment to read the following [[Usecase>>doc:Main.eMagiz Academy.Use Cases.Pattern Determination.WebHome||target="blank"]]
50 +Take a moment to read the following [[Use Case>>doc:Main.eMagiz Academy.Use Cases.Pattern Determination.WebHome||target="blank"]]. If you are interested in this topic and want more information on it please read the help text provided by eMagiz and read the following links:
51 +* [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
52 +** [[Crash Course Event Streaming (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.WebHome||target="blank"]]
53 +*** [[Introduction (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.crashcourse-eventstreaming-event-streaming-introduction||target="blank"]]
54 +** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]]
55 +*** [[API Gateway - Introduction (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-introduction||target="blank"]]
58 58  
59 -== 7. Silent demonstration video ==
60 -
61 -As this is a more theoretical microlearning, we have no video that accompanies this microlearning.)))((({{toc/}}))){{/container}}{{/container}}
57 +)))((({{toc/}}))){{/container}}{{/container}}