Skip to Content
Last modified by Erik Bakker on 2024/09/02 16:11
From version 16.1
edited by Erik Bakker
on 2022/06/13 13:31
Change comment: Renamed from xwiki:Migrated Pages fundamentals.eMagiz API Gateway
To version 11.1
edited by eMagiz
on 2022/06/13 09:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.marijn
Content
... ... @@ -1,4 +1,7 @@
1 -{{container}}{{container layoutStyle="columns"}}(((
1 +{{html wiki="true"}}
2 +<div class="ez-academy">
3 + <div class="ez-academy_body">
4 +<div class="doc">
2 2  
3 3  
4 4  
... ... @@ -8,6 +8,9 @@
8 8  
9 9  Should you have any questions, please get in touch with academy@emagiz.com.
10 10  
14 +* Last update: November 10th, 2021
15 +* Required reading time: 10 minutes
16 +
11 11  == 1. Prerequisites ==
12 12  * Some context on API Management will be helpful.
13 13  
... ... @@ -21,7 +21,7 @@
21 21  
22 22  The eMagiz API Gateway is the pattern in which a specific entry point is made available for external applications (users). These external applications can connect to this entry point via a series of operations. These operations are listed in a manner that allows this application user to retrieve data or provide data. Users & Roles are managed on a central level to control access to the various data sources.
23 23  
24 -[[image:Main.Images.Fundamental.WebHome@fundamental-api-gateway-introduction-1.png]]
30 +<p align="center">[[image:fundamental-api-gateway-introduction-1.png||]]</p>
25 25  
26 26  === 3.1 Entry point for application users ===
27 27  The entry point is a REST/JSON-based web service publicly accessible via the eMagiz Cloud for external application users. There is no other type of web service possible, and all the operations inside this web service are all REST/JSON based. In eMagiz, this concept translates into an All Entry flow type.
... ... @@ -29,16 +29,16 @@
29 29  === 3.2 Operations ===
30 30  An operation is defined as an entry point in the API Gateway that allows a specific type of interaction with the data exposed. For instance, a user wants to get the data for a particular order or create an order via this entry point. In this example, there will be a GET Order and a POST Order operation. The traditional HTTP operations, such as GET, POST, and PUT, are possible * see the below figure for the complete list.
31 31  
32 -[[image:Main.Images.Fundamental.WebHome@fundamental-api-gateway-introduction-2.png]]
38 +<p align="center">[[image:fundamental-api-gateway-introduction-2.png||]]</p>
33 33  
34 34  === 3.3 API Providers & Transformation ===
35 35  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.
36 36  
37 -[[image:Main.Images.Fundamental.WebHome@fundamental-api-gateway-introduction-4.png]]
43 +<p align="center">[[image:fundamental-api-gateway-introduction-4.png||]]</p>
38 38  
39 39  Each operation can have a Gateway Message and a System message for the specific API. In this way, standard eMagiz transformation tooling is made available to handle content and format transformations in the API Gateway.
40 40  
41 -[[image:Main.Images.Fundamental.WebHome@fundamental-api-gateway-introduction-5.png]]
47 +<p align="center">[[image:fundamental-api-gateway-introduction-5.png||]]</p>
42 42  
43 43  === 3.4 Interaction type & error handling ===
44 44  The API Gateway follows a synchronous pattern which means there is always a request being made to the web service, and that same web service will always provide you with a response. The web service will wait until the backend system delivering the response is ready to send that response.
... ... @@ -53,7 +53,7 @@
53 53  === 3.6 API Disovery ===
54 54  External application users can discover the operations via an online Portal * the SwaggerUI technology is used for that purpose. In that online section, the user can see all the published operations. For operation, all the required information is displayed to understand how to connect to the API correctly. That includes the request and response definitions, parameters, naming, response codes, and many more. Once the credentials have been provided, the application user can try out the operation.
55 55  
56 -[[image:Main.Images.Fundamental.WebHome@fundamental-api-gateway-introduction-3.png]]
62 +<p align="center">[[image:fundamental-api-gateway-introduction-3.png||]]</p>
57 57  
58 58  
59 59  === 3.6 Architectural components ===
... ... @@ -60,10 +60,10 @@
60 60  
61 61  A simplified picture below illustrates the overall architecture of API Gateway in the eMagiz Cloud.
62 62  
63 -[[image:Main.Images.Fundamental.WebHome@fundamental-api-gateway-introduction-6.png]]
69 +<p align="center">[[image:fundamental-api-gateway-introduction-6.png||]]</p>
64 64  
71 +===== Practice =====
65 65  
66 -
67 67  == 4. Key takeaways ==
68 68  
69 69  * API Gateway can serve as a single entry point for all external or intern application users
... ... @@ -85,6 +85,10 @@
85 85  
86 86  == 6. Silent demonstration video ==
87 87  
88 -{{video attachment="fundamental-api-gateway-introduction.mp4" reference="Main.Videos.Fundamental.WebHome"/}}
94 +<iframe width="1280" height="720" src="../../vid/fundamental/APIGW_Fundamental.mp4" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
89 89  
90 -)))((({{toc/}}))){{/container}}{{/container}}
96 +
97 +</div>
98 +</div>
99 +</div>
100 +{{/html}}
fundamental-api-gateway-introduction-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ebakker
Size
... ... @@ -1,1 +1,0 @@
1 -13.3 KB
Content