Changes for page Understanding Design Architecture

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,7 +1,6 @@
1	1	{{container}}
2	2	{{container layoutStyle="columns"}}
3	3	(((
4		-
5	5	In a previous microlearning on this [[subject>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-understanding-design-architecture-basic.WebHome||target="blank"]] we have learned the basics of the Design Architecture overview. In this microlearning, we will expand our knowledge of Design Architecture. This is to get an even better understanding of what the Design Architecture overview is about and how you can best utilize this within the context of your project(s). Having this knowledge will make it easier to make a correct architectural decision in the long haul.
6	6
7	7	Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
...	...	@@ -23,8 +23,6 @@
23	23	* Impact / Consequence of changing something in Design Architecture
24	24	* Why do Design and Deploy Architecture differ from each other (in some cases)
25	25
26		-
27		-
28	28	== 3. Understanding Design Architecture ==
29	29
30	30	In a previous microlearning on this [[subject>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-understanding-design-architecture-basic.WebHome||target="blank"]] we have learned the basics of the Design Architecture overview. In this microlearning, we will expand our knowledge of Design Architecture. This is to get an even better understanding of what the Design Architecture overview is about and how you can best utilize this within the context of your project(s). Having this knowledge will make it easier to make a correct architectural decision in the long haul.
...	...	@@ -48,7 +48,7 @@
48	48
49	49	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).
50	50
51		-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](expert-solution-architecture-determining-needed-memory.md). 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.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.
52	52
53	53	=== 3.3 Impact of changes ===
54	54
...	...	@@ -59,15 +59,16 @@
59	59	In the previous segment, we talked about the impact of changing things in Design Architecture. In this segment, we will look at some scenarios in which the Design Architecture view can differ from the Deploy Architecture view. There are three main reasons why both of them differ:
60	60
61	61	* This is the first time you open Deploy Architecture
62		- * This means you need to spin up your cloud infrastructure for the first time
	59	+* This means you need to spin up your cloud infrastructure for the first time
63	63	* There is no flow related to the runtime embedded in the release
64		- * Runtimes won't show up in Deploy Architecture when no flow should be deployed on them within the currently active release
65		- * Note that this can differ per environment
	61	+* Runtimes won't show up in Deploy Architecture when no flow should be deployed on them within the currently active release
66	66	* The runtime is excluded in Design Architecture
67		- * With this functionality, you explicitly mention that a certain runtime should not be deployed
	63	+* With this functionality, you explicitly mention that a certain runtime should not be deployed
68	68
69	69	Knowing this should make you better equipped to handle 'unexpected' situations you occur while implementing your data model with the help of the eMagiz platform.
70	70
	67	+{{info}}Note that the reason why you see a specific runtime can differ per environment.{{/info}}
	68	+
71	71	== 4. Assignment ==
72	72
73	73	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.
...	...	@@ -80,8 +80,6 @@
80	80	* Impact / Consequence of changing something in Design Architecture
81	81	* Why do Design and Deploy Architecture differ from each other (in some cases)
82	82
83		-
84		-
85	85	== 6. Suggested Additional Readings ==
86	86
87	87	If you are interested in this topic and want more information on it please read the help texts provided by eMagiz
...	...	@@ -88,8 +88,7 @@
88	88
89	89	== 7. Silent demonstration video ==
90	90
91		-As this is a more theoretical microlearning we have no video for this
92		-)))
	87	+As this is a more theoretical microlearning we have no video for this)))
93	93
94	94	((({{toc/}}))){{/container}}
95	95	{{/container}}