Skip to Content

Changes for page API Gateway Architecture

Last modified by Erik Bakker on 2024/09/02 16:04
From version 4.1
edited by Erik Bakker
on 2022/06/13 08:07
Change comment: There is no comment for this version
To version 3.1
edited by Erik Bakker
on 2022/06/13 08:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -22,7 +22,7 @@
22 22  === 3.1 Cloud approval ===
23 23  The eMagiz team will provide approval on what type of Cloud your model has access to. In the figure below you can see the first column where the number of machines for a specific T*shirt size are allowed. The Cloud approval can be done by your eMagiz partner and is based on the licensed eMagiz Cloud. Once in the edit modus of the Design architecture, you can assign the available Cloud machine to a specific Core or Connector machine in the architecture.
24 24  
25 -[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-consequence-size-cloud-1.png]]
25 +[[image:Main.Images.Microlearning.WebHome@advanced*solution*architecture*consequence*size*cloud*1.png]]
26 26  
27 27  === 3.2 Cloud t-shirt sizing ===
28 28  eMagiz provides the following sizing for the Cloud slots. The memory is mentioned below as that is the key driver for upgrading to bigger sizing.
... ... @@ -34,7 +34,7 @@
34 34  
35 35  === 3.3 Cloud sizing advice ===
36 36  
37 -In the [microlearning](crashcourse-platform-design-understanding-design-architecture-basic.md) you can see how to the current machines can be reviewed for available memory.
37 +In the [microlearning](crashcourse*platform*design*understanding*design*architecture*basic.md) you can see how to the current machines can be reviewed for available memory.
38 38  
39 39  === 3.4 Impact of Cloud sizing ===
40 40  
... ... @@ -42,7 +42,7 @@
42 42  
43 43  1. Count 762 Mb overhead for the machine
44 44  2. Count 100 Mb per runtime on the machine
45 -3. Count the tables for the runtime head and non*heap memory according to NL. See this [microlearning](expert-solution-architecture-determining-needed-memory.md) for more information
45 +3. Count the tables for the runtime head and non*heap memory according to NL. See this [microlearning](expert*solution*architecture*determining*needed*memory.md) for more information
46 46  
47 47  This count is also handy when verifying the actual assigned values in Deploy Architecture.
48 48  
... ... @@ -53,7 +53,7 @@
53 53  1. Change sizing values of topics (retention size).
54 54  2. Exclude topics * which effectively means that these no longer count towards the configured size and if effectuated in the Deploy will be deleted. This feature is handy to use in the lifecycle of topics from test to acceptance to production. Topics in test can be excluded in case the topic is already in production.
55 55  
56 -[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-consequence-size-cloud-2.png]]
56 +[[image:Main.Images.Microlearning.WebHome@advanced*solution*architecture*consequence*size*cloud*2.png]]
57 57  
58 58  
59 59