Skip to Content
Version 1.1 by Erik Bakker on 2022/06/13 08:04
Show last authors
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.
3
4 Should you have any questions, please contact academy@emagiz.com.
5
6 * Last update: October 20th, 2021
7 * Required reading time: 10 minutes
8
9 == 1. Prerequisites ==
10 * Intermediate knowledge of the eMagiz platform
11 * Good working experience in the Design and Deploy Architecture phase.
12
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
15
16
17
18 == 3. Specific eMagiz runtime considerations ==
19
20 === 3.1 Messaging pattern runtimes ===
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.
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 ===
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)
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.
37
38
39
40
41 == 4. Assignment ==
42
43 There is no specific assignment as this is more theoretical microlearning.
44
45 == 5. Key takeaways ==
46 Take into account the key considerations for each case to ensure the runtime is placed on the right location.
47
48
49
50 == 6. Suggested Additional Readings ==
51
52 There are no suggested additional readings on this topic
53
54 == 7. Silent demonstration video ==
55
56 There is no demonstration video of this functionality.
57
58 )))((({{toc/}}))){{/container}}{{/container}}