Changes for page eMagiz Architecture

Last modified by Carlijn Kokkeler on 2024/08/08 15:21

From version 13.1
edited by eMagiz
on 2022/07/06 15:36
Change comment: There is no comment for this version
To version 6.1
edited by eMagiz
on 2022/07/06 15:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,25 +17,16 @@
17 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.
18 18  
19 19  === 3.1 Solution Architecture ===
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.
21 -
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.
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.
23 23  
24 24  [[image:Main.Images.Fundamental.WebHome@fundamental_architecture-1.png]]
25 25  
26 26  === 3.2 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.
25 +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"]]
28 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 +
30 30  
31 - ** Design Architecture **
32 - [[image:Main.Images.Fundamental.WebHome@fundamental_architecture-2.png]]
33 -
34 - ** Deploy Architecture **
35 - [[image:Main.Images.Fundamental.WebHome@fundamental_architecture-3.png]]
36 36  
37 -
38 -
39 39  == 4. Key takeaways ==
40 40  
41 41  * Data models define the structure of data related to a system or related to eMagiz itself
... ... @@ -42,20 +42,16 @@
42 42  * Within a data model, you model out the relationships between entities
43 43  * Within a data model, you define all relevant attributes of an entity
44 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 -
47 47  
48 48  
38 +
49 49  == 5. Suggested Additional Readings ==
50 50  
51 -If you are interested in this topic and want to learn more, please check out the microlearnings mentioned below.
52 -
53 -* [[Basic Design Architecture>>Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
54 -* [[Novice Cloud Management>>Main.eMagiz Academy.Microlearnings.Novice.eMagiz Cloud Management.WebHome||target="blank"]]
55 -* [[Intermediate Solution Architecture>>Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.WebHome||target="blank"]]
56 -* [[Intermediatew Cloud Management>>Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.WebHome||target="blank"]]
57 -* [[Advanced Solution Architecture>>Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.WebHome||target="blank"]]
58 -* [[Advanced Cloud Management>>Main.eMagiz Academy.Microlearnings.Advanced Level.eMagiz Cloud Management.WebHome||target="blank"]]
59 -* [[Expert Solution Architecture>>Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.WebHome||target="blank"]]
41 +If you are interested in this topic and want to learn how you can control your Cloud with the help of the eMagiz platform, please check out our microlearnings offering on eMagiz Cloud Management:
60 60  
43 +* [[Understanding the eMagiz CDM>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-what-is-cdm.WebHome||target="blank"]]
44 +* [[API Data Model>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-api-data-model.WebHome||target="blank"]]
45 +* [[Event Streaming Data Model>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Configuring Event Streaming.intermediate-configuring-event-streaming-data-model.WebHome||target="blank"]]
46 +* https://afteracademy.com/blog/what-are-the-different-types-of-relationships-in-dbms
47 +
61 61  )))((({{toc/}}))){{/container}}{{/container}}