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		-advanced-solution-architecture-consequence-size-cloud
	1	+Key differences Design & Deploy Architecture

Content

...	...	@@ -1,49 +1,63 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
2		-This microlearning will focus on some considerations for putting the eMagiz runtime at the right location in the architecture.
	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 20th, 2021
7		-* Required reading time: 10 minutes
	6	+* Last update: April 7th, 2022
	7	+* Required reading time: 5 minutes
8	8
9	9	== 1. Prerequisites ==
10	10	* Intermediate knowledge of the eMagiz platform
11		-* Good working experience in the Design and Deploy Architecture phase.
	11	+* Good working experience in the Design & Deploy architecture aspects
12	12
13	13	== 2. Key concepts ==
14		-In the various microlearnings until the intermediate level, we have explained the eMagiz runtime (https://emagiz.github.io/docs/microlearning/crashcourse*platform*deploy*install*local*connector). In short, it is the process that can make the flow components operational and execute the designated tasks of that flow. Please refer to these microlearnings for further information
	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. Specific eMagiz runtime considerations ==
	18	+== 3. Key differences in views Deploy & Design ==
19	19
20		-=== 3.1 Messaging pattern runtimes ===
	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		-For Messaging specific patterns the runtime should be placed in such a way that there is connectivity between that runtime and the sending/receiving system. The system might be located in a Cloud service or Cloud VPC that eMagiz clients are hosting. Or are located on*premises of the client. Here are the options and advice for putting the runtime.
	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:
23	23
24		-1. Sender or Receiver system is located in a public or private Cloud
25		- * Put the Runtime on a Cloud Connector machine and ensure to use the connectivity options provided in eMagiz
26		-
27		-2. Sender or Receiver system is located in a DMZ section of the client infrastructure
28		- * Put the runtime inside the same DMZ zone to keep the runtime as close to the system as possible
29		- * Ensure the management of the runtime is something workable for the client. Consider the updates that may occur as well as the fact that the runtime can no longer be managed by the eMagiz Portal
30		-
31		-=== 3.2 API Gateway pattern runtimes ===
	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:
32	32
33		-For these runtime the first choice is put all the Gateway Entry Flow and the Exit gates on the Cloud Connector machine. This way, the number of runtimes are kept to a minimum and there is full control over these runtime. In the exceptional case where the exit gate needs to connect to a system that is not accessible via the client firewalls, you can opt to put these exit gates only on a runtime that can be deployed on*premises. Please refer to the [microlearning around running part of the solution locally](advanced*api*management*running*part*of*your*api*gateway*solution*on*premise)
	27	+[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-diffs-design-deploy-1.png]]
34	34
35		-=== 3.3 Event Streaming pattern runtimes ===
36		-In the case where Event processors are used in the Event Streaming solution designed, eMagiz provides a event streaming container (runtime). This runtime can only run in a Cloud-based machine, and only in the core machines of eMagiz. The key reason is that these Event Processors need to connect to the topics that are only available in the eMagiz Cloud and not accessible from outside the eMagiz VPC. Any runtime that is consuming or producing data with these topics needs to have the capability to access such topics.
	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.
37	37
	32	+[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-diffs-design-deploy-2.png]]
38	38
	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.
39	39
	37	+[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-diffs-design-deploy-3.png]]
40	40
	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
	40	+
	41	+[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-diffs-design-deploy-4.png]]
	42	+
	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
	45	+
	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.
	48	+
	49	+[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-diffs-design-deploy-4.png]]
	50	+
	51	+
	52	+
	53	+
41	41	== 4. Assignment ==
42	42
43		-There is no specific assignment as this is more theoretical microlearning.
	56	+Please experiment with the options in eMagiz Design & Deploy Architecture to understand the above points.
44	44
	58	+
45	45	== 5. Key takeaways ==
46		-Take into account the key considerations for each case to ensure the runtime is placed on the right location.
	60	+Design and Deploy architecture can differ in view * specific reasons exit which are described in this microlearning.
47	47
48	48
49	49