Skip to Content

Changes for page API Gateway Architecture

Last modified by Erik Bakker on 2024/09/02 16:04
From version 19.3
edited by Danniar Firdausy
on 2024/08/07 10:01
Change comment: There is no comment for this version
To version 16.1
edited by Erik Bakker
on 2023/01/23 10:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Content
... ... @@ -53,7 +53,7 @@
53 53  
54 54  === 3.4 Hybrid Cloud setup ===
55 55  
56 -In the [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.API Management.advanced-api-management-running-part-of-your-api-gateway-solution-on-premise||target="blank"]] you can find the reasons and configuration for running the exit gates in on-premises runtimes. A view of such a architecture is displayed here:
56 +In the [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.API Management.advanced-api-management-running-part-of-your-api-gateway-solution-on-premise.WebHome||target="blank"]] you can find the reasons and configuration for running the exit gates in on-premises runtimes. A view of such a architecture is displayed here:
57 57  
58 58  [[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-apigw-architecture-4.png]]
59 59  
... ... @@ -61,19 +61,22 @@
61 61  
62 62  For now the memory requirements for API Gateway are the same as for Messaging flows. Please refer to the [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory||target="blank"]].
63 63  
64 -== 4. Key takeaways ==
64 +== 4. Assignment ==
65 65  
66 -* API Gateways can be part of a hybrid landscape that combines the available integration patterns.
67 -* A single lane setup is usually sufficient for most cases.
68 -* Hybrid setups are possbible but please be sure the ask the right questions before implementing such.
66 +There is no specific assignment for now. The correct use of the Design architecture is explained in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-understanding-design-architecture-basic||target="blank"]].
69 69  
70 -== 5. Suggested Additional Readings ==
68 +== 5. Key takeaways ==
71 71  
72 -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:
73 -* [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
74 -** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]]
75 -*** [[API Gateway - Introduction (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-introduction.WebHome||target="blank"]]
70 +* API Gateways can be part of a mixed landscape of Messaging, Event Streaming and API Gateways
71 +* A single lane setup is usually sufficient for most cases
72 +* Hybrid setups are possbible but please be sure the ask the right questions before implementing such
76 76  
74 +== 6. Suggested Additional Readings ==
77 77  
76 +There are no suggested additional readings on this topic
78 78  
78 +== 7. Silent demonstration video ==
79 +
80 +There is no demonstration video of this functionality.
81 +
79 79  )))((({{toc/}}))){{/container}}{{/container}}