Changes for page Architectural Runtime Decisions
Last modified by Erik Bakker on 2024/09/02 16:02
From version 16.1
edited by Carlijn Kokkeler
on 2024/08/27 12:39
on 2024/08/27 12:39
Change comment:
There is no comment for this version
To version 17.1
edited by Carlijn Kokkeler
on 2024/08/29 10:41
on 2024/08/29 10:41
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,8 +1,10 @@ 1 1 {{container}} 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 - This microlearningwill focusonsomeconsiderationsforputtingthe eMagiz runtimeatthe right locationinthe architecture.4 +In previous microlearnings up to the intermediate level, we've covered the fundamentals of the eMagiz runtime—the process that makes flow components operational and ensures tasks are executed as designed. For a deeper understanding, refer back to those lessons. 5 5 6 +Now, we'll explore specific considerations for placing the runtime in different scenarios. Whether dealing with messaging patterns, API gateways, or event streaming, the location of your runtime is crucial for connectivity and performance. Each case requires careful planning to ensure the runtime is optimally positioned, whether in the cloud, on-premises, or within specific network zones. 7 + 6 6 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 7 7 8 8 == 1. Prerequisites ==