Skip to Content
Last modified by Erik Bakker on 2024/09/02 16:11
From version 26.2
edited by Erik Bakker
on 2024/02/01 08:34
Change comment: Update document after refactoring.
To version 24.1
edited by Erik Bakker
on 2022/06/13 13:38
Change comment: Deleted image "fundamental-api-gateway-introduction-6.png"

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -fundamental-emagiz-introduction
1 +eMagiz API Gateway
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.eMagiz Academy.Fundamentals.WebHome
1 +WebHome
Content
... ... @@ -24,7 +24,7 @@
24 24  [[image:Main.Images.Fundamental.WebHome@fundamental-api-gateway-introduction-2.png]]
25 25  
26 26  === 3.3 API Providers & Transformation ===
27 -There is a specific system connected to the operation for every operation, which gets the data or processes the data. That system, application, or service is geared towards that specific piece of data and may have its connectivity requirements, security requirement, or data structure. eMagiz will create a particular Exit Gate Flow type so that all these requirements can be appropriately handled. In the figure below the Control Tower, Exact, AFAS, and Address validator are the API providers.
27 +There is a specific system connected to the operation for every operation, which gets the data or processes the data. That system, application, or service is geared towards that specific piece of data and may have its connectivity requirements, security requirement, or data structure. eMagiz will create a particular Exit Gate Flow type so that all these requirements can be appropriately handled. The figure below the Control Tower, Exact, AFAS, and Address validator are the API providers.
28 28  
29 29  [[image:Main.Images.Fundamental.WebHome@fundamental-api-gateway-introduction-4.png]]
30 30