Skip to Content
Last modified by Danniar Firdausy on 2024/09/16 15:40
From version 10.1
edited by Erik Bakker
on 2023/01/23 08:41
Change comment: There is no comment for this version
To version 13.1
edited by Carlijn Kokkeler
on 2024/08/08 15:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -45,7 +45,7 @@
45 45  
46 46  The runtime is the component into which the individual integration flows are deployed. It's a Java-based application container that can run in the Cloud or Local. A runtime is visually displayed and described in the eMagiz iPaaS Portal as a process container (holding the onramps, offramps, routing, error), an event streaming container (holding the event processors), a gateway container (holding all entry and the exit gates), or a connector (holding the exits and entries).
47 47  
48 -One critical element in Design Architecture is determining how many runtimes can run on a specific machine. For a detailed explanation on that, I would like to refer you to the following [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory.WebHome||target="blank"]]. As a general rule of thumb, we use a placeholder of 1GB of memory per runtime. That means that roughly speaking you can safely place 8 runtimes on an L machine. You will notice that when you dig into the numbers deeper the number can shift based on the actual implementation.
48 +One critical element in Design Architecture is determining how many runtimes can run on a specific machine. For a detailed explanation on that, I would like to refer you to the following [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory||target="blank"]]. As a general rule of thumb, we use a placeholder of 1GB of memory per runtime. That means that roughly speaking you can safely place 8 runtimes on an L machine. You will notice that when you dig into the numbers deeper the number can shift based on the actual implementation.
49 49  
50 50  === 3.3 Impact of changes ===
51 51  
... ... @@ -66,12 +66,8 @@
66 66  
67 67  {{info}}Note that the reason why you see a specific runtime can differ per environment.{{/info}}
68 68  
69 -== 4. Assignment ==
69 +== 4. Key takeaways ==
70 70  
71 -Read up on the release notes of the various platform components and determine for the projects in which you operate what the status is of your eMagiz solution on the eMagiz platform.
72 -
73 -== 5. Key takeaways ==
74 -
75 75  * Key considerations when dealing with Design Architecture are:
76 76   * Approval (Cloud, Topic Storage, etc.)
77 77   * Ratio between size and number of runtimes (Golden ratio)
... ... @@ -78,14 +78,13 @@
78 78   * Impact / Consequence of changing something in Design Architecture
79 79   * Why do Design and Deploy Architecture differ from each other (in some cases)
80 80  
81 -== 6. Suggested Additional Readings ==
77 +== 5. Suggested Additional Readings ==
82 82  
83 -If you are interested in this topic and want more information on it please read the help texts provided by eMagiz
79 +* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
80 +** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
81 +*** [[Understanding Design Architecture - Basic (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-understanding-design-architecture-basic||target="blank"]]
82 +)))
84 84  
85 -== 7. Silent demonstration video ==
86 -
87 -As this is a more theoretical microlearning we have no video for this)))
88 -
89 89  ((({{toc/}}))){{/container}}
90 90  {{/container}}
91 91