Last modified by Erik Bakker on 2023/08/23 15:28
Show last authors
1 {{container}}{{container layoutStyle="columns"}}(((
2 This microlearning will focus on the aspects of eMagiz Cloud and sizing of the Cloud
3
4 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5
6 == 1. Prerequisites ==
7 * Intermediate knowledge of the eMagiz platform
8 * Good working experience in the Design & Deploy architecture aspects
9
10 == 2. Key concepts ==
11 The eMagiz Cloud is the set of services and machines that make up together the engine in which the integrations are made active. Please refer to the [[eMagiz Cloud Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-event-streaming-introduction||target="blank"]] to learn about that Cloud infrastructure.
12
13 == 3. eMagiz Cloud sizing ==
14
15 eMagiz provides insight into the required sizing of the machines and runtimes in the Design architecture. Objective is to configure the proper size of the Cloud machines so that the designed architecture can actually be effectuated.
16
17 === 3.1 Cloud approval ===
18 The eMagiz team will provide approval on what type of Cloud your model has access to. In the figure below you can see the first column where the number of machines for a specific T-shirt size are allowed. The Cloud approval can be done by your eMagiz partner and is based on the licensed eMagiz Cloud. Once in the edit modus of the Design architecture, you can assign the available Cloud machine to a specific Core or Connector machine in the architecture.
19
20 [[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-consequence-size-cloud-1.png]]
21
22 {{warning}}Note that we currently do not offer any cloud machines anymore with a t-shirt size above XL. Therefore your partner manager will never approve any proposed machine sizing of XXL.{{/warning}}
23
24 === 3.2 Cloud t-shirt sizing ===
25 eMagiz offers the following sizing for the Cloud slots. The memory is mentioned below as that is the key driver for upgrading to bigger sizing.
26
27 1. S size **> 2Gb memory per machine
28 2. M size **> 4Gb memory per machine
29 3. L size **> 8Gb memory per machine
30 4. XL size **> 16Gb memory per machine
31
32 === 3.3 Cloud sizing advice ===
33
34 In the [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-understanding-design-architecture-basic||target="blank"]] you can see how your current machine(s) can be reviewed for available memory.
35
36 === 3.4 Impact of Cloud sizing ===
37
38 The actual assigned machine size will be implemented in the Deploy architecture. In case your total runtime and machines are consuming more than the available memory of that specific size, the runtimes will not properly load and become disfunctional. To determine overcommitted cloud machines, use the following calculation mechnanism
39
40 1. Count 762 Mb overhead for the machine
41 2. Count 100 Mb per runtime on the machine
42 3. Do a summation of the total configured heap and non-heap memory of all runtimes assigned to that machine. See this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory||target="blank"]] for more information
43
44 This count is also handy when verifying the actual assigned values in Deploy Architecture.
45
46 === 3.5 Managing sizing of Event topics ===
47
48 In the Design architecture you can manage your sizing of Event Streaming topics. eMagiz sees the topics as part of the Cloud infrastructure. Right clicking the topic storage in Design Architecture, would lead to the following screen - see fiugure below. Options available are:
49
50 1. Change sizing values of topics (retention size).
51 2. Exclude topics
52 ** This effectively means that these no longer count towards the configured size and if effectuated in the Deploy will be deleted. This feature is handy to use in the lifecycle of topics from test to acceptance to production. Topics in test can be excluded in case the topic is already in production.
53
54 [[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-consequence-size-cloud-2.png]]
55
56 == 4. Key takeaways ==
57 Part of the eMagiz platform is the Cloud which has specific upper limits for sizing. Understanding these helps to understand the impact of the designed architecture and to decide to influence these upper limits by expanding the sizing to a higher range.
58
59 == 5. Suggested Additional Readings ==
60
61 There are no suggested additional readings on this topic)))((({{toc/}}))){{/container}}{{/container}}