Changes for page Understanding Design Architecture

Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.eMagiz
	1	+XWiki.ebakker

Default language

...	...	@@ -1,0 +1,1 @@
	1	+en

Content

...	...	@@ -1,14 +1,10 @@
1	1	{{container}}
2	2	{{container layoutStyle="columns"}}
3	3	(((
	4	+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.
4	4
5		-In a previous microlearning on this [subject](crashcourse-platform-design-understanding-design-architecture-basic.md) 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	+Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6	6
7		-Should you have any questions, please contact academy@emagiz.com.
8		-
9		-* Last update: July 27th, 2021
10		-* Required reading time: 6 minutes
11		-
12	12	== 1. Prerequisites ==
13	13
14	14	* Basic knowledge of the eMagiz platform
...	...	@@ -26,11 +26,9 @@
26	26	* Impact / Consequence of changing something in Design Architecture
27	27	* Why do Design and Deploy Architecture differ from each other (in some cases)
28	28
29		-
30		-
31	31	== 3. Understanding Design Architecture ==
32	32
33		-In a previous microlearning on this [subject](crashcourse-platform-design-understanding-design-architecture-basic.md) 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.
	27	+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.
34	34
35	35	The focal point of this microlearning will be to provide context on the Design Architecture page:
36	36
...	...	@@ -51,7 +51,7 @@
51	51
52	52	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).
53	53
54		-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.
55	55
56	56	=== 3.3 Impact of changes ===
57	57
...	...	@@ -83,8 +83,6 @@
83	83	* Impact / Consequence of changing something in Design Architecture
84	84	* Why do Design and Deploy Architecture differ from each other (in some cases)
85	85
86		-
87		-
88	88	== 6. Suggested Additional Readings ==
89	89
90	90	If you are interested in this topic and want more information on it please read the help texts provided by eMagiz
...	...	@@ -91,8 +91,7 @@
91	91
92	92	== 7. Silent demonstration video ==
93	93
94		-As this is a more theoretical microlearning we have no video for this
95		-)))
	86	+As this is a more theoretical microlearning we have no video for this)))
96	96
97	97	((({{toc/}}))){{/container}}
98	98	{{/container}}