Changes for page API Gateway Architecture
Last modified by Erik Bakker on 2024/09/02 16:04
From version 17.1
edited by Erik Bakker
on 2023/08/23 15:31
on 2023/08/23 15:31
Change comment:
There is no comment for this version
To version 22.1
edited by Carlijn Kokkeler
on 2024/08/29 10:44
on 2024/08/29 10:44
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,5 +1,5 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 - This microlearning willfocusoncribing the generalarchitecture of theAPIGateway. After this microlearning,thebackgroundofthe API GWarchitectureshould be clear2 +In this microlearning, we’ll explore key architectural considerations for setting up API Gateways within eMagiz. We'll cover the basic concepts of single-lane and double-lane setups, which refer to the number of runtimes used and their role in ensuring system reliability. Additionally, we'll look at different architecture configurations, including how to position runtimes in the Cloud and on-premises environments, and the memory requirements for these setups. Understanding these aspects will help you design a robust and efficient API Gateway architecture. 3 3 4 4 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 5 5 ... ... @@ -63,10 +63,19 @@ 63 63 64 64 == 4. Key takeaways == 65 65 66 -* API Gateways can be part of a mixed landscapeof Messaging, EventStreamingdAPI Gateways67 -* 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 +* 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. 69 69 70 70 == 5. Suggested Additional Readings == 71 71 72 -There are no suggested additional readings on this topic)))((({{toc/}}))){{/container}}{{/container}} 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||target="blank"]] 76 +*** [[Setting up Exit gate (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-setting-up-exit-gate||target="blank"]] 77 +* [[Expert (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]] 78 +** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.WebHome||target="blank"]] 79 +*** [[How to Determine Needed Memory (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory||target="blank"]] 80 + 81 +)))((({{toc/}}))){{/container}}{{/container}}