Skip to Content
Last modified by Erik Bakker on 2024/09/02 16:02
From version 4.1
edited by Erik Bakker
on 2022/10/03 11:26
Change comment: There is no comment for this version
To version 8.1
edited by Erik Bakker
on 2023/08/23 15:24
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Architectural Runtime Descisions
1 +Architectural Runtime Decisions
Content
... ... @@ -1,7 +1,7 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 2  This microlearning will focus on some considerations for putting the eMagiz runtime at the right location in the architecture.
3 3  
4 -Should you have any questions, please contact academy@emagiz.com.
4 +Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
6 6  == 1. Prerequisites ==
7 7  * Intermediate knowledge of the eMagiz platform
... ... @@ -14,14 +14,14 @@
14 14  
15 15  === 3.1 Messaging pattern runtimes ===
16 16  
17 -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.
17 +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.
18 18  
19 -1. Sender or Receiver system is located in a public or private Cloud
20 - * Put the Runtime on a Cloud Connector machine and ensure to use the connectivity options provided in eMagiz
19 +* Sender or Receiver system is located in a public or private Cloud
20 +** Put the Runtime on a Cloud Connector machine and ensure to use the connectivity options provided in eMagiz
21 21  
22 -2. Sender or Receiver system is located in a DMZ section of the client infrastructure
23 - * Put the runtime inside the same DMZ zone to keep the runtime as close to the system as possible
24 - * 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
22 +* Sender or Receiver system is located in a DMZ section of the client infrastructure
23 +** Put the runtime inside the same DMZ zone to keep the runtime as close to the system as possible
24 +** 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
25 25  
26 26  === 3.2 API Gateway pattern runtimes ===
27 27  
... ... @@ -30,19 +30,9 @@
30 30  === 3.3 Event Streaming pattern runtimes ===
31 31  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.
32 32  
33 -== 4. Assignment ==
34 -
35 -There is no specific assignment as this is more theoretical microlearning.
36 -
37 -== 5. Key takeaways ==
33 +== 4. Key takeaways ==
38 38  Take into account the key considerations for each case to ensure the runtime is placed on the right location.
39 39  
40 -== 6. Suggested Additional Readings ==
36 +== 5. Suggested Additional Readings ==
41 41  
42 -There are no suggested additional readings on this topic
43 -
44 -== 7. Silent demonstration video ==
45 -
46 -There is no demonstration video of this functionality.
47 -
48 -)))((({{toc/}}))){{/container}}{{/container}}
38 +There are no suggested additional readings on this topic)))((({{toc/}}))){{/container}}{{/container}}