Skip to Content
Last modified by Danniar Firdausy on 2024/09/30 17:12
From version 35.6
edited by Danniar Firdausy
on 2024/09/05 10:35
Change comment: There is no comment for this version
To version 35.8
edited by Danniar Firdausy
on 2024/09/18 13:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,6 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 2  
3 -In our [[crash course>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]] on the API Gateway pattern, we have learned about setting up the API Gateway. However, we still need to delve into how to update your existing API Gateway solution. In this microlearning, we will focus on updating the design phase of your API gateway (and the subsequent steps) and the create phase of your API gateway (and subsequent steps). This is to learn the impact of updates and how we can achieve this.
3 +Building on what we covered in our [[crash course>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]] about setting up the API Gateway, we will now focus on the next critical step: updating your existing API Gateway solution. In this microlearning, we will guide you through the process of updating both the design phase and the create phase of your API Gateway, and explore how these updates impact your solution.
4 4  
5 5  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6 6  
... ... @@ -11,13 +11,8 @@
11 11  == 2. Key concepts ==
12 12  
13 13  This microlearning centers around updating your API Gateway.
14 +* By updating, we mean: changing existing software to reflect new insights or ideas that have come up during development and testing.
14 14  
15 -By updating, we mean changing existing software to reflect new insights or ideas that have come up during development and testing.
16 -
17 -* Updating can happen from Design
18 -* Updating can happen from Create
19 -* Both situations have a different impact
20 -
21 21  == 3. Updating your API Gateway Operations ==
22 22  
23 23  In our [[crash course>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]] on the API Gateway pattern, we have learned about setting up the API Gateway. However, we still need to delve into how to update your existing API Gateway solution. In this microlearning, we will focus on updating the design phase of your API gateway (and the subsequent steps) and the create phase of your API gateway (and subsequent steps). This is to learn the impact of updates and how we can achieve this.
... ... @@ -58,13 +58,13 @@
58 58  
59 59  == 4. Key takeaways ==
60 60  
61 -* Updating can happen from Design
62 -* Updating can happen from Create
63 -* Both situations have a different impact
64 -* Adding a new operation to an existing solution does not involve a reset
65 -* Updating from Create does not involve a reset
66 -* Updating from Design does not involve a reset
56 +* Updates to your API Gateway can be made either during the Design phase or the Create phase, each with distinct impacts.
57 +* Changes made in the Design phase affect the configuration of the entry gate and may necessitate updates to both entry and exit gates, depending on the nature of the changes.
58 +* Changes during the Create phase typically involve modifications to gateway messages, with changes reflected automatically in the Swagger definition and a version bump of the infra flow.
59 +* Adding new operations or updating from either Design or Create does not require a reset of the existing solution.
60 +* Ensure that updates are included in the deployment phase to reflect the latest changes in the Swagger file and runtime infra flow.
67 67  
62 +
68 68  == 5. Suggested Additional Readings ==
69 69  
70 70  If you are interested in this topic and want more information, please read the help text provided by eMagiz and see the following link: