Changes for page Key differences Design & Deploy Architecture

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Consequences of cloud size changes and cloud approval
	1	+Key differences Design & Deploy Architecture

Content

...	...	@@ -1,9 +1,9 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
2		-This microlearning will focus on the aspects of eMagiz Cloud and sizing of the Cloud
	2	+This micro-learning will focus on some differences between the Design and Deploy architecture
3	3
4	4	Should you have any questions, please contact academy@emagiz.com.
5	5
6		-* Last update: October 21st, 2021
	6	+* Last update: April 7th, 2022
7	7	* Required reading time: 5 minutes
8	8
9	9	== 1. Prerequisites ==
...	...	@@ -11,60 +11,53 @@
11	11	* Good working experience in the Design & Deploy architecture aspects
12	12
13	13	== 2. Key concepts ==
14		-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 Fundamentals to learn about that Cloud infrastructure.
	14	+The Design Architecture is the place where the architecture of the integration model is forged. It allows to place Systems to Cloud or On-premises connector machines so that hybrid cloud architectures are possible. The Deploy Architecture is the place where the Design architecture is effectuated. In case a system is added to a Cloud Connector machine for instance, the Deploy architecture will allows to actually deploy that runtime.
15	15
16	16
17	17
18		-== 3. eMagiz Cloud sizing ==
	18	+== 3. Key differences in views Deploy & Design ==
19	19
20		-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.
	20	+The System is the key notion for a eMagiz runtime to get created. The eMagiz runtime is a Java based application container in which flows can be made active or operational. In most cases, all Systems in Design are to be located on a machine to effectuate these runtimes on the machines.
21	21
22		-=== 3.1 Cloud approval ===
23		-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.
	22	+However, in some cases the Deploy architecture looks different compared to the Design architecture. In a sense that some system don't get "created" in Deploy. These are the reasons for Systems not to appear in Deploy architecture:
24	24
25		-[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-consequence-size-cloud-1.png]]
	24	+* System is only used for API Gateway Access
	25	+The system acts as a role and user, and no other integrations are used to and from that system. You can recognize the blue lines with blue rounded boxes containing the number of operations. These systems will be displayed in Design yet not in Deploy architecture. No runtime application is needed as no flows are supposed to run inside these systems. Multi-tenant systems that act as role (with tenants being the users) are also not displayed as system in Deploy Architecture. Below an example of such a case:
26	26
27		-=== 3.2 Cloud t-shirt sizing ===
28		-eMagiz provides the following sizing for the Cloud slots. The memory is mentioned below as that is the key driver for upgrading to bigger sizing.
	27	+[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-diffs-design-deploy-1.png]]
29	29
30		-1. S size **> 2Gb memory per machine
31		-2. M size **> 4Gb memory per machine
32		-3. L size **> 8Gb memory per machine
33		-4. XL size **> 16Gb memory per machine
34		-
35		-=== 3.3 Cloud sizing advice ===
	29	+* System that is used only for Event Streaming integrations
	30	+The same applies to systems that are displayed for registering Producers and Consumers for Event Streaming. These systems are not displayed in Deploy Architecture.
36	36
37		-In the [microlearning](crashcourse-platform-design-understanding-design-architecture-basic.md) you can see how to the current machines can be reviewed for available memory.
	32	+[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-diffs-design-deploy-2.png]]
38	38
39		-=== 3.4 Impact of Cloud sizing ===
	34	+* Systems accessed via Exit Gates only
	35	+Applications that accessed via API Gateway operations only are also no displayed in the Deploy Architecture. Exit gates are accessing these applications (displayed as systems) yet the exit gate will run on the gateway container runtime. Therefore, these system don't require any flow to deploy on so no runtimes gets created.
40	40
41		-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
	37	+[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-diffs-design-deploy-3.png]]
42	42
43		-1. Count 762 Mb overhead for the machine
44		-2. Count 100 Mb per runtime on the machine
45		-3. Count the tables for the runtime head and non*heap memory according to NL. See this [microlearning](expert-solution-architecture-determining-needed-memory.md) for more information
	39	+There is an exception for that. In case the exit gate is required to run on the on-premises infrastructure of the client for security reasons, the runtime does get created and will be displayed therefore in the Deploy architecture. Apply to environment will not result in the physical deployment of the runtime, but's displayed so that the Deployment plan can indicate progress on deployment. The option Split Gateway needs to be checked in the Design phase
46	46
47		-This count is also handy when verifying the actual assigned values in Deploy Architecture.
	41	+[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-diffs-design-deploy-4.png]]
48	48
49		-=== 3.5 Managing sizing of Event topics ===
	43	+* Hybrid systems
	44	+In case a system will contain not only a user management like integration but also another integration (i.e. Messaging) the runtime will be displayed in Deploy architecture as usual. A flow or series of flows need to be deployed on the runtime
50	50
51		-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:
	46	+* Best practice for Design Architecture
	47	+In Design Architecture it is adviced to create one or more on-premises machine that is toggled excluded. Each of these machine will act as a location where runtime not used in Deploy are put. So alignment between Design and Deploy is improved.
52	52
53		-1. Change sizing values of topics (retention size).
54		-2. Exclude topics * which 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.
	49	+[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-diffs-design-deploy-4.png]]
55	55
56		-[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-consequence-size-cloud-2.png]]
57	57
58	58
59	59
60		-
61	61	== 4. Assignment ==
62	62
63		-Please experiment with the options in eMagiz Design architecture to understand the above points.
	56	+Please experiment with the options in eMagiz Design & Deploy Architecture to understand the above points.
64	64
65	65
66	66	== 5. Key takeaways ==
67		-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.
	60	+Design and Deploy architecture can differ in view * specific reasons exit which are described in this microlearning.
68	68
69	69
70	70