Changes for page eMagiz Architecture

Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -9,40 +9,47 @@
9	9
10	10	== 2. Key concepts ==
11	11
12		-All concepts are discussed in the section below.
	12	+TBA
13	13
	14	+
14	14	== 3. Architecture in eMagiz ==
15	15
16		-In this fundamental, we will zoom in on explaining the concepts and terms related to Architecture incorporated within the eMagiz platform. At first, we will look at the "Solution Architecture" within the platform, and subsequently, we will look at the "Cloud Architecture."
	17	+In this fundamental, we will zoom in on what data models are and how they are used within the various integration patterns we support in the platform. Then, we start our journey with a more theoretical look at the concept of data models. Following, we will zoom in on each of the three integration patterns. Finally, per integration pattern, we will explain the role of the data model within each of these three patterns.
17	17
18	18	=== 3.1 Solution Architecture ===
19		-In most phases, there is visualization present in the product that describes the integration landscape. In Capture, Design, Create and Deploy, you will have this primarily visual, and each phase displays the integration landscape for that specific phase. So that the integration landscape is better understood in the context of the phase. We refer to these views as solution views as it tries to describe how the data is flowing from system to system. In other words, what solution is used for the business process.
	20	+In most phase, there is visualization present in the product that describes the integration landscape. In Capture, Design, Create and Deploy you will have this visual mostly, and each phase does display the integration landscape particular for that specific phase. So that the integration landscape is better understood in the context of the phase. We refer these views as solution views as it tries to describe how the data is flowing from system to system. Or what solution is used for the business process.
20	20
21		-Below is an example you can recognize as a screenshot of a design phase. Such views are helpful in discussion with users and architects involved in the integration work.
22		-
	22	+Below an example you can recognize as a screenshot of a Design phase. Such views are helpful in discussion with users and architectx involved in the integration work.
	23	+
23	23	[[image:Main.Images.Fundamental.WebHome@fundamental_architecture-1.png]]
24	24
25	25	=== 3.2 Cloud Architecture ===
26		-For this, we mean the specific way the eMagiz runtimes are distributed on infrastructure components such as the eMagiz Cloud, on-premises servers, or other locations where runtime may exist. Please take a moment to check out the Fundamental of Cloud architecture via this [[link>>https://docs.emagiz.com/bin/view/Main/eMagiz%20Academy/Fundamentals/fundamental-emagiz-cloud-inner-workings||target="blank"]]. Below is a high-level view of Cloud architecture.
	27	+For this we mean the specific way the eMagiz runtimes are distributed on infrastructure components such as the eMagiz Cloud, on-premises servers or other locations where runtime may exist. Please take a moment to check out the Fundamental on Cloud architecture via this [[link>>https://docs.emagiz.com/bin/view/Main/eMagiz%20Academy/Fundamentals/fundamental-emagiz-cloud-inner-workings||target="blank"]]. Below an high level view of a Cloud architecture.
	28	+
	29	+The Cloud architecture can be design in the Design - Architecture section, and effectuated via the Deploy - Architecture section. Please check out the microlearnings mentioned below for more information on the way to configure these or how to make the right architecture descisions.
27	27
28		-The Cloud architecture can be designed in the Design - Architecture section and effectuated via the Deploy - Architecture section. Please check out the microlearnings mentioned below for more information on how to configure these or make the right architecture decisions.
29		-
30	30	**Design Architecture**
31	31	[[image:Main.Images.Fundamental.WebHome@fundamental_architecture-2.png]]
32		-
	33	+
33	33	**Deploy Architecture**
34	34	[[image:Main.Images.Fundamental.WebHome@fundamental_architecture-3.png]]
35	35
	37	+
	38	+
36	36	== 4. Key takeaways ==
37	37
38		-* The Solution architecture is present in most phases of eMagiz and describes how systems are interconnected and how the data is flowing between these systems
39		-* Each phase will have a slightly different representation of the solution architecture that provides context on the particular phase
40		-* The Cloud architecture in eMagiz describes how the runtime are distributed over the different infrastructures such as Cloud and on-premises.
	41	+* Data models define the structure of data related to a system or related to eMagiz itself
	42	+* Within a data model, you model out the relationships between entities
	43	+* Within a data model, you define all relevant attributes of an entity
	44	+* eMagiz uses data models in each of the patterns to structure the data (flow)
	45	+[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-cloud-inner-workings--high-overview.png]]
	46	+
41	41
	48	+
42	42	== 5. Suggested Additional Readings ==
43	43
44	44	If you are interested in this topic and want to learn more, please check out the microlearnings mentioned below.
45		-
	52	+
46	46	* [[Basic Design Architecture>>Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
47	47	* [[Novice Cloud Management>>Main.eMagiz Academy.Microlearnings.Novice.eMagiz Cloud Management.WebHome||target="blank"]]
48	48	* [[Intermediate Solution Architecture>>Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.WebHome||target="blank"]]