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
Change comment: There is no comment for this version
To version 18.2
edited by Danniar Firdausy
on 2024/08/07 09:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -63,10 +63,14 @@
63 63  
64 64  == 4. Key takeaways ==
65 65  
66 -* API Gateways can be part of a mixed landscape of Messaging, Event Streaming and API Gateways
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 +* 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 +
75 +
76 +)))((({{toc/}}))){{/container}}{{/container}}