Skip to Content

Changes for page API Gateway Architecture

Last modified by Erik Bakker on 2024/09/02 16:04
From version 12.1
edited by Erik Bakker
on 2022/10/03 11:31
Change comment: There is no comment for this version
To version 13.1
edited by Erik Bakker
on 2023/01/23 10:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -22,11 +22,11 @@
22 22  [[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-apigw-architecture-1.png]]
23 23  
24 24  Key notes
25 -1. Gateway runtime
25 +* Gateway runtime
26 26  The Gateway has a separate runtime where the associated gateway flows are deployed in. The exit gates and all entry flow are the typical flow types present in this runtime, next to the usual infrastructure flow
27 -2. Location runtime
27 +* Location runtime
28 28  The Gateway runtime is located in a Cloud machine, and is specifically put on the Connector machine. The Connector machine has the ability to allow incoming data (secured) traffic from outside the Virtual Private Cloud that each client has. The Core machine does not have this option due to security reasons. The eMagiz Cloud handles the proper and secure routing to the API gateway.
29 -3. Gateway only runtime
29 +* Gateway only runtime
30 30  These are system that act as application user of 1 or more operations made available in the API Gateway. In case the system is only connected in the Design phase as such an application user, than that system only acts as input for User Management. The system doesn't need to be deployed as a runtime on the Connector machine, and should therefore be placed on an excluded machine. In the picture above, Exact online is such a system.
31 31  
32 32  === 3.2 Single lane Cloud setup ===