Skip to Content
Last modified by Danniar Firdausy on 2024/09/05 12:36
Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}
3 (((
4 In this microlearning, we'll explore the concept of "Design Architecture" and how it can assist you in managing your integration landscape. "Design Architecture" refers to the overview of where your instances are deployed, which machines they're running on, and the resources required for deployment. By understanding this overview, you'll gain insights into where your instances are located (cloud or on-premise), the machine sizes needed, and whether you have the capacity to develop more integration solutions within your current setup.
5
6 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7
8 == 1. Prerequisites ==
9
10 * Basic knowledge of the eMagiz platform
11
12 == 2. Key concepts ==
13
14 This microlearning centers around understanding what the Design Architecture overview is and how it can help you.
15
16 With Design Architecture we mean: The desired overview of where the instances are deployed, on which machines, and how many resources it takes to deploy these instances.
17
18 The Design Architecture gives you insights into:
19
20 * Where do my instances run (cloud, on-premise)
21 * What is the machine size needed to run my instances
22 * Can I still develop more integration solutions within the current sizing parameters
23
24 == 3. Understanding Design Architecture ==
25
26 The Design Architecture overview is accessible under Design. In Design, you can click on Architecture to get to the overview.
27 The following Design Architecture could look similar to what you would see the first time you open this page. A lot to improve as you can see.
28
29 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-understanding-design-architecture-basic--rough-overview.png]]
30
31 As you can see in the overview of the architecture we have several machines within our integration landscape (i.e. localhost, local machine, External 01, etc.) and each machine has several systems running on it.
32
33 === 3.1 Core Machine ===
34
35 The machine called localhost in this example is a so-called core machine. This machine (or machines if you scale up) plays host to the core functionalities of eMagiz:
36
37 * JMS
38 * Process Container (holds all onramps, offramps, routers, and the error process for messaging processes)
39 * Event Streaming Container (holds all onramps and offramps for event stream processes)
40
41 Depending on your specific implementation you need some of them or all of them. If you do not need them you can exclude them. As a result, eMagiz will grey them out indicating that the system in question can be ignored.
42
43 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-understanding-design-architecture-basic--core-machine.png]]
44
45 === 3.2 Connector Machine(s) ===
46
47 The machine called a local machine in this example is a so-called connector machine.
48 These machines are the place where you exchange data with other systems. As this is the place to connect to other systems internet connectivity is a must.
49
50 Within eMagiz we make a distinction between two types of connector machine(s):
51
52 * Connector machine(s) running in the eMagiz Cloud managed by eMagiz
53 * Connector machine(s) running on-premise in the data center of the client
54
55 Both are also represented differently within this picture. The on-premise systems are blue and behind one firewall.
56
57 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-understanding-design-architecture-basic--on-prem-connector-machine.png]]
58
59 The connector machine(s) in the eMagiz Cloud is running in between firewalls and are green.
60
61 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-understanding-design-architecture-basic--emagiz-cloud-connector-machine.png]]
62
63 Cleaning the picture up and removing the unnecessary systems gives us a way nicer overview
64
65 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-understanding-design-architecture-basic--nice-overview.png]]
66
67 === 3.3 Determining size ===
68
69 Apart from determining where an instance (runtime) should be running (cloud or on-premise) the Design Architecture
70 also helps in determining the size a machine would need to have to support the processes running on it.
71
72 When you activate the Start Editing mode you will notice that you can alter the size of the green machines (those that are managed by eMagiz)
73
74 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-understanding-design-architecture-basic--core-machine-start-editing.png]]
75
76 To help you determine the size of the machine eMagiz has the option to check the size status
77
78 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-understanding-design-architecture-basic--check-size-status.png]]
79
80 In the pop-up that follows we specify how the memory advice of eMagiz is calculated (the figure on the left above a machine).
81 This can help you determine the correct sizing for your machine, now and in the future
82
83 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-understanding-design-architecture-basic--check-size-status-popup.png]]
84
85 There is much more to tell about Design Architecture but more on that in later microlearnings.
86
87 == 4. Key takeaways ==
88
89 * Design Architecture gives you context on which instances run where (on-premise or cloud)
90 * Design Architecture gives you the tools that you need to determine the correct sizing for your environment
91 * Machines are divided into so-called core and connector machines
92
93 == 5. Suggested Additional Readings ==
94
95 * [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]
96 ** [[eMagiz Architecture (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-architecture.WebHome||target="blank"]]
97 ** [[Discovery (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-discovery.WebHome||target="blank"]]
98 ** [[Multi-Model Explained (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-multi-model-explained.WebHome||target="blank"]]
99 ** [[Multi-Model Best Practice (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-multi-model-best-practice.WebHome||target="blank"]]
100 * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
101 ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
102 *** [[Storing Metadata - Design Architecture (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-storing-metadata||target="blank"]]
103 *** [[Settings (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-project-settings||target="blank"]]
104 ** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]]
105 *** [[Finishing the Design Phase (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-finishing-the-design-phase.WebHome||target="blank"]]
106 * [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
107 ** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.WebHome||target="blank"]]
108 *** [[Understanding Design Architecture (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.intermediate-solution-architecture-understanding-design-architecture||target="blank"]]
109 ** [[Lifecycle Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Lifecycle Management.WebHome||target="blank"]]
110 *** [[Cleanup Design Architecture (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Lifecycle Management.intermediate-lifecycle-management-cleanup-design-architecture||target="blank"]]
111 * [[Advanced (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.WebHome||target="blank"]]
112 ** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.WebHome||target="blank"]]
113 *** [[Architectural Runtime Decisions (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.advanced-solution-architecture-runtime-decision.WebHome||target="blank"]]
114 *** [[Key differences Design & Deploy Architecture (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.advanced-solution-architecture-diffs-design-deploy.WebHome||target="blank"]]
115 *** [[Consequences Of Cloud Size (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.advanced-solution-architecture-consequence-size-cloud.WebHome||target="blank"]]
116 * [[Expert (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]]
117 ** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.WebHome||target="blank"]]
118 *** [[How to Determine Needed Memory (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory||target="blank"]]
119 * [[Design Architecture (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=1%2FMain.eMagiz+Academy.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22design+architecture%22||target="blank"]]
120 )))
121
122 (((
123 {{toc/}}
124 )))
125 {{/container}}
126 {{/container}}