Changes for page eMagiz Runtime Generation 3

Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.CarlijnKokkeler
	1	+XWiki.ebakker

Content

...	...	@@ -27,14 +27,12 @@
27	27
28	28	A more modern technology compared to traditional servers is to use Docker containers. Docker provides containers that mimic servers in a specific way. A container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another. A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries and settings.
29	29
30		-Container images become containers at runtime and in the case of Docker containers images become containers when they run on Docker Engine. From eMagiz we provide Linux based images that represent the code that processes your messages. As Docker is agnostic in terms of OS the solution can run in our cloud and on-premise on both Linux and Windows-based servers. Containers isolate software from its environment and ensure that it works uniformly despite differences for instance between development and staging.
	30	+Container images become containers at runtime and in the case of Docker containers * images become containers when they run on Docker Engine. Available for both Linux and Windows-based applications, containerized software will always run the same, regardless of the infrastructure. Containers isolate software from its environment and ensure that it works uniformly despite differences for instance between development and staging.
31	31
32	32	The runtime of eMagiz can run inside a Docker, and the runtime is made part of the docker image. In the docker image you will find other required pieces such as OS, Java, monitoring services, etc.
33	33
34	34	[[image:Main.Images.Fundamental.WebHome@fundamental-runtime-generation3-2.png]]
35	35
36		-{{info}}More information on the install process of on-premise Docker can be found [[here>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-installguide.WebHome||target="blank"]]{{/info}}
37		-
38	38	=== 3.4 Impact on Way of Working Gen2 vs. Gen3 ===
39	39
40	40	{{info}}See the additional readings for more detailed information on these changes and how you can migrate from the current situation to the new situation.{{/info}}
...	...	@@ -53,7 +53,6 @@
53	53
54	54	* Build number
55	55	The notion of build numbers no longer exists in the new runtime. Or not so explicitly as before. The Docker image will load the required libraries when creating the runtime image, and always use the latest.
56		- It is strongly advised to have all flows on the latest build number before starting the migration.
57	57
58	58	* Error handling
59	59	The error handling on flow level will change in comparison to the current generation. In the new generation we will offer two options.